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

Raymond Hettinger python at rcn.com
Tue Nov 10 00:24:56 CET 2009

>. Further, the developer controlling the code
> just may not care -- the script can be for single use, for a class project,
> or some other purpose that doesn't require being notified of what may
> change in a later version of Python.

[Geremy Condra debatem1 at gmail.com]
> If they don't care, why does it matter whether they see it or not?

There is a difference about not caring about the content of the warning
versus caring about whether the messages clutter the screen.  Noise is always bad.
There are legitimate reasons for not being interested in what is going to change
in a future version of Python -- for those people, the messages are a distraction and nuisance.


More information about the stdlib-sig mailing list