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 < 1.9 are > unsupported at which point you could update the import to the new location > without needing a conditional. > > On Monday, October 26, 2015 at 10:29:02 AM UTC-4, Carlton wrote: >> >> 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 >> imported from `forms` or should we (conditionally) update the import now >> (whilst we have the issue open)? >> >> Thanks! >> >> Carlton >> >> 1: https://github.com/maraujop/django-crispy-forms/pull/518 >> 2: >> https://github.com/django/django/commit/a51070e7434426467869147608c5a8ca58e21e00 >> 3: >> https://github.com/django/django/blob/master/docs/releases/1.9.txt#L370-L371 >> >>
-- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/11305ede-d165-428f-b669-e2ecaa744f10%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
