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

Yuvgoog Greenle ubershmekel at gmail.com
Mon Nov 9 09:12:38 CET 2009

On Mon, Nov 9, 2009 at 9:31 AM, Laura Creighton <lac at openend.se> wrote:
> Because casual programmers are not motivated to go after Deprecation
> Warnings
[ snip ]
> So lots of DeprecationWarnings
> will only train them to ignore DeprecationWarnings, or all Warnings.
> Laura
> _______________________________________________
> stdlib-sig mailing list
> stdlib-sig at python.org
> http://mail.python.org/mailman/listinfo/stdlib-sig

This isn't just about casual programmers, everybody who uses python on
a daily basis for just interpreter stuff, are they supposed to change
their interpreter shortcut to have the warnings option just to stay up
to date ?

Not everyone that uses python is a package designer with unit tests
and a buildbot that runs with all the most advanced configurations
(that show hidden warnings).

This warning hiding feature's just making python a bit more of a "dark
art of the few who know it well". What ever happened to "unless
explicitly silenced"?


More information about the stdlib-sig mailing list