[Python-Dev] When to remove deprecated stuff (was: Deprecating the formatter module) (original) (raw)

Ezio Melotti ezio.melotti at gmail.com
Fri Aug 16 01:23:24 CEST 2013

On Thu, Aug 15, 2013 at 3:40 PM, Brett Cannon <brett at python.org> wrote:

On Thu, Aug 15, 2013 at 8:36 AM, Antoine Pitrou <solipsis at pitrou.net>wrote:

> A number of us (I don't know how many) have clearly been thinking about > "Python 4" as the time when we remove cruft. This will not cause any > backward compatibility issues for anyone who has paid heed to the > deprecation warnings, but will for those who haven't.

Which is why we shouldn't silence deprecation warnings. What we should probably do is have unittest turn deprecations on by default when running your tests but leave them silent otherwise.

http://bugs.python.org/issue10535 (I put the keys of the time machine back at their usual place)

Best Regards, Ezio Melotti

I still think keeping them silent for the benefit of end-users is a good thing as long as we make it easier for developers to switch on warnings without thinking about it.

-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20130816/e19893f5/attachment.html>

More information about the Python-Dev mailing list