RetroSearch Browse

Fri Nov 10 04:51:06 EST 2017 · https://mail.python.org/pipermail/python-dev/2017-November/150448.html

On Tue, Nov 7, 2017 at 8:45 AM, Nathaniel Smith <njs at pobox.com> wrote:
> Also, IIRC it's actually impossible to set the stacklevel= correctly when
> you're deprecating a whole module and issue the warning at import time,
> because you need to know how many stack frames the import system uses.

Doh, I didn't remember correctly. Actually Brett fixed this in 3.5:
https://bugs.python.org/issue24305

-n

-- 
Nathaniel J. Smith -- https://vorpus.org

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

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

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