[Python-Dev] Proposal: go back to enabling DeprecationWarning by default (original) (raw)
Ethan Furman ethan at stoneleaf.us
Tue Nov 7 09:21:38 EST 2017
- Previous message (by thread): [Python-Dev] Proposal: go back to enabling DeprecationWarning by default
- Next message (by thread): [Python-Dev] Proposal: go back to enabling DeprecationWarning by default
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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
- Previous message (by thread): [Python-Dev] Proposal: go back to enabling DeprecationWarning by default
- Next message (by thread): [Python-Dev] Proposal: go back to enabling DeprecationWarning by default
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]