On Sun, Dec 13, 2009 at 8:13 AM, Jerome Leclanche <[email protected]> wrote: > +1 from me too on the timeline, but why the PendingDeprecationWarning? > I don't see the point, there isnt exactly a limit to how long > something can be deprecated.
PendingDeprecationWarning lets us introduce the change gradually. * PendingDeprecationWarnings aren't actually visible to the end user unless the turn on the -W flag to the Python interpreter * DeprecationWarning is visible by default. By making the change over three releases, it gives plenty of code-level warnings that a change is going to happen, including a period where you can be warned of the change at your option. Yours, Russ Magee %-) -- 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.
