[stdlib-sig] standardizing the deprecation policy (and how noisy they are)

Michael Foord michael at voidspace.org.uk
Sun Nov 8 22:51:12 CET 2009

Guido van Rossum wrote:
> [snip...]
> On Sun, Nov 8, 2009 at 1:35 PM, Michael Foord <michael at voidspace.org.uk> wrote:
>> Almost no-one is ever going to run Python with PendingDeprecation
>> warnings switched on, so there should be at least one 'noisy' release in
>> my opinion.
> I disagree. The -3 option is an example of a better approach: silent
> by default, warnings enabled by a command line flag. If we can trust
> developers to use -3 to check for Py3k incompatibilities, we should
> also be able to trust them to check for deprecation warnings
> explicitly.
> (Another argument to think about: if you download and install some 3rd
> party code, deprecation warnings about that code are *only noise*
> since they are not yours to fix. Warnings in a dynamic language work
> very different than warnings in a compiled language.)
Sounds like a good argument. The downside is that code 'just stops 
working' with no *apparent* warning.



More information about the stdlib-sig mailing list