1.9 Changes to BoundField

[Carlton]

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

[Tim Graham]

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.

[Carlton]

Thank you. Spot on answer. C.