This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author njs
Recipients barry, gregory.p.smith, jwilk, miss-islington, nascheme, njs, rhettinger, serhiy.storchaka, steven.daprano, terry.reedy, xiang.zhang
Date 2018-12-01.01:44:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> In my experience people are more likely to run code through a linter than they are to ever run an interpreter with DeprecationWarning enabled.

This used to be true, and it was a disaster. So there's been a lot of work to fix it, and it's not true anymore.

Starting in 3.7, the built-in REPL has DeprecationWarning enabled by default, as do all standalone scripts (see PEP 565).

IPython/Jupyter has enabled DeprecationWarning by default for interactive code for about 3 years now:

pytest started showing DeprecationWarnings by default a few months ago, and unittest has done so for ages.

I don't think I've ever met someone who skipped straight to linting, without ever having used a REPL, or written a script, or written a test :-)
Date User Action Args
2018-12-01 01:45:00njssetrecipients: + njs, barry, nascheme, rhettinger, terry.reedy, gregory.p.smith, jwilk, steven.daprano, serhiy.storchaka, xiang.zhang, miss-islington
2018-12-01 01:45:00njssetmessageid: <>
2018-12-01 01:45:00njslinkissue34850 messages
2018-12-01 01:44:59njscreate