On Thursday 31 January 2013, Byron Ruth wrote: > Here is the ticket: https://code.djangoproject.com/ticket/19668 and the > pull request https://github.com/django/django/pull/674 > > One user commented on the ticket raising a concern that it could possibly > be misused if the data is set after it had been used. It is certainly a > valid concern, however it should be made clear in the docs when to use it > and/or raise an exception if `is_valid` has already been called. > > Thoughts?
While this is backwards-compatible per se, using it in views is generally not backwards-compatible with user form classes (you can't tell what they do in their initializers); thus, generic views (and also some not-generic views) are forced to keep using the "old way" unless the (user) form code is altered. Which means, you'll have two ways to do the same thing (in views), without a clear preference between them. So if you want this judged as a backwards-compatible change, I'm -1. As a non-backwards-compatible change, I'd like it, but I don't think it's worth the disruption, so I'm -0. Either way, I'm not a core dev. Shai. -- You received this message because you are subscribed to the Google Groups "Django developers" 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
