[Python-Dev] Proposal: go back to enabling DeprecationWarning by default (original) (raw)

Paul Moore p.f.moore at gmail.com
Tue Nov 7 09:27:16 EST 2017

On 7 November 2017 at 14:21, Ethan Furman <ethan at stoneleaf.us> wrote:

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".

OK, I overstated. Apologies. My recollection is of a lot more end user complaints when deprecation warnings were previously switched on than others seem to remember, but I can't find hard facts, so I'll assume I'm misremembering.

Paul

More information about the Python-Dev mailing list