I'm guessing it's the standard way to do things and this may be a bit offtopic but still, out of curiousity, since the PendingDepWarning is not visible by default doesn't this actually give the users just the illusion of more time to fix their code?
Django releases are, from what I can see, getting a lot faster than Python ones. A commandline switch to enable specific warnings makes sense for python itself, but for Django itself, someone who just regularly runs svn update every 4-5 months and has some bad luck with timing may know about the warning only a very short time before the release. Maybe I'm just digging in the paint, but to me it would make a lot more sense to disable warnings with a command line switch rather than enable them and have a note around the lines of DeprecationWarning: The pycopg1 backend will be removed in Django 1.4. You may disable this warning with --some-switch. (Disclaimer: I never use warnings) J. Leclanche / Adys On Sat, Dec 12, 2009 at 6:22 PM, Russell Keith-Magee <freakboy3...@gmail.com> wrote: > On Sun, Dec 13, 2009 at 8:13 AM, Jerome Leclanche <adys...@gmail.com> 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 django-develop...@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
