Home Original page

[Python-Dev] Deprecation policy

Antoine Pitrou solipsis at pitrou.net
Sun Jan 26 15:59:53 CET 2014 
On Sat, 25 Jan 2014 18:30:24 -0800
Raymond Hettinger <raymond.hettinger at gmail.com> wrote:
> 
> On Jan 25, 2014, at 5:29 AM, Ezio Melotti <ezio.melotti at gmail.com> wrote:
> 
> > Nick also suggested to document
> > our deprecation policy in PEP 5 (Guidelines for Language Evolution:
> > http://www.python.org/dev/peps/pep-0005/ ).
> 
> Here's a few thoughts on deprecations:
> 
> * If we care at all about people moving to Python 3, then we'll stop
> doing anything that makes the process more difficult.  For someone
> moving from Python 2.7, it really doesn't matter if something that
> existed in 2.7 got deprecated in 3.1 and removed in 3.3; from their
> point-of-view, it just one more thing that won't work.

+1.

> * The notion of PendingDeprecationWarnings didn't work out very well.
> Conceptually, it was a nice idea, but in practice no one was benefitting
> from it.  The warnings slowed down working, but not yet deprecated code.
> And no one was actually seeing the pending deprecations.

+1 too, especially since DeprecationWarnings are now silent by default,
there's no reason to start with a PendingDeprecationWarning IMO.

Regards

Antoine.
More information about the Python-Dev mailing list