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

[Antoine Pitrou]

Le lundi 09 novembre 2009 à 15:09 -0800, Raymond Hettinger a écrit :
> 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.

If it's for single use or for a class project, you are certainly using
up-to-date constructs which won't emit any deprecation warning. The
issue of deprecation warnings should only appear when you write
something that gets used for more than a year or two.