Thank you. Spot on answer. C.
On Monday, 26 October 2015 15:55:03 UTC+1, Tim Graham wrote:
>
> The release notes don't mention it because it's a private API until now.
> Feel free to do nothing as we're unlikely to remove the backwards
> compatibility alias for a while, at least until versions <
The release notes don't mention it because it's a private API until now.
Feel free to do nothing as we're unlikely to remove the backwards
compatibility alias for a while, at least until versions < 1.9 are
unsupported at which point you could update the import to the new location
without needin
Hi.
We've got a PR open on Crispy Forms to accommodate the changes to
BoundField's location in 1.9. It changed, broke the imports and was then
imported back for compatibility.
The release notes say very little here.
Could anyone who knows the plan say, whether BoundField should still be
imp
