On 7/30/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > That sounds like the best thing to do -- I don't see a huge need to > deprecate maxlength immediately, or even issue warnings about it. The > change gets a +1 from me.
I'd say that making maxlength issue a PendingDeprecationWarning -- which is suppressed by default -- is probably worth the time. That way people who want to update their code immediately can easily find where maxlength is still used. Then in the next release we can change that to a DeprecationWarning (which is loud by default) and then finally remove it a release after that. But I'm really just bike-shedding now; I'm +1 check the patch in with or without these changes. Jacob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
