[Python-Dev] [python-committers] Enabling depreciation warnings feature code cutoff (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Tue Nov 7 20:35:13 EST 2017
- Previous message (by thread): [Python-Dev] [python-committers] Enabling depreciation warnings feature code cutoff
- Next message (by thread): [Python-Dev] [python-committers] Enabling depreciation warnings feature code cutoff
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 8 November 2017 at 10:03, Guido van Rossum <guido at python.org> wrote:
OK, so let's come up with a set of heuristics that does the right thing for those cases specifically. I'd say whenever you're executing code from a zipfile or some such it's not considered your own code (by default).
My current preferred heuristic is just to add a new default filter to the list:
once::DeprecationWarning:__main__
Which says to warn specifically for the main module, and continue ignoring everything else.
That way ad hoc scripts and the REPL will get warnings by default, while zipapps and packages can avoid warnings by keeping their main.py simple, and importing a CLI helper function from another module. Entry point wrapper scripts will implicitly have the same effect for installed packages.
If folks want to get warnings for other modules as well, then they can either pass "-Wd" to get warnings for everything, or else enable them selectively using the default main module filter as an example.
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] [python-committers] Enabling depreciation warnings feature code cutoff
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]