On Wed, Feb 25, 2015 at 8:51 AM, Serhiy Storchaka <storchaka@gmail.com> wrote:
What you are think about turning deprecation warnings on by default in the interactive interpreter?

Deprecation warnings are silent by default because they just annoys end user that uses old Python program with new Python. End user usually is not a programmer and can't do something with warnings. But in the interactive interpreter the user is the author of executed code and can avoid to use deprecated functions if warned.

Python-ideas mailing list
Code of Conduct: http://python.org/psf/codeofconduct/

Am I the only one thinking that disabling deprecation warnings by default (2.6?) was a bad idea?
It's particularly counterproductive for library vendors and their users because the latters have no visibility of what APIs are going to be removed: they will just wake up one day, upgrade to the next major version of their favorite lib and have their code broken.