RetroSearch Browse

Tue Nov 7 09:21:38 EST 2017 · https://mail.python.org/pipermail/python-dev/2017-November/150311.html

On 11/07/2017 05:44 AM, Paul Moore wrote:

> If you're a user and your application developer didn't do (1) or a
> library developer developing one of the libraries your application
> developer chose to use didn't do (2), you're hosed. If you're a user
> who works in an environment where moving to a new version of the
> application is administratively complex, you're hosed.

Suffering from DeprecationWarnings is not "being hosed".  Having your script/application/framework suddenly stop working 
because nobody noticed something was being deprecated is "being hosed".

+1 to turn them back on.

--
~Ethan~

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2017-November/150311.html below:

[Python-Dev] Proposal: go back to enabling DeprecationWarning by default