[Python-Dev] [python-committers] Enabling depreciation warnings feature code cutoff (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Thu Nov 9 23:49:13 EST 2017
- Previous message (by thread): [Python-Dev] [python-committers] Enabling depreciation warnings feature code cutoff
- Next message (by thread): [Python-Dev] Reminder: 12 weeks to 3.7 feature code cutoff
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 10 November 2017 at 14:34, Greg Ewing <greg.ewing at canterbury.ac.nz> wrote:
Tres Seaver wrote:
IIUC, that would be as expected: you would see the warnings when running your test suite exercising that imported code (which should run with all warnings enabled), but not when running the app. But then what benefit is there in turning on deprecation warnings automatically for main?
Not all code has test suites, most notably:
- code entered at the REPL
- personal automation scripts
- single file Python scripts (as opposed to structured applications)
The tests for these are generally either "Did it do what I wanted?" or else a dry-run mode where it prints out what it would have done in normal operation.
Cheers, Nick.
-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message (by thread): [Python-Dev] [python-committers] Enabling depreciation warnings feature code cutoff
- Next message (by thread): [Python-Dev] Reminder: 12 weeks to 3.7 feature code cutoff
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]