A RetroSearch Logo

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

Search Query:

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

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

[Python-Dev] Proposal: go back to enabling DeprecationWarning by defaultEric V. Smith eric at trueblade.com
Mon Nov 6 19:44:03 EST 2017
On 11/6/2017 1:12 PM, Barry Warsaw wrote:
> On Nov 5, 2017, at 20:47, Nick Coghlan <ncoghlan at gmail.com> wrote:
> 
>>> warnings.silence_deprecations()
>>> python -X silence-deprecations
>>> PYTHONSILENCEDEPRECATIONS=x
>>
>> It could be interesting to combine this with Tim's suggestion of
>> putting an upper version limit on the silencing, so the above may look
>> like:
>>
>>     warnings.ignore_deprecations((3, 7))
>>     python -X ignore-deprecations=3.7
>>     PYTHONIGNOREDEPRECATIONS=3.7
> 
> That could be cool as long as we also support wildcards, e.g. defaults along the lines of my suggestions above to ignore everything.

I'd like to see a command line or environment variable that says: "turn 
on deprecation warnings (and/or pending deprecation warnings), but do 
not show warnings for this list of modules (possibly regex's)".

Like:
PYTHONDEPRECATIONWARNINGSEXCEPTFOR=PIL,requests.*

Then I'd just turn it on for all modules (empty string?), and when I got 
something that was flooding me with output I'd add it to the list.

Eric.
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4