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 gregory.p.smith
Recipients barry, gregory.p.smith, jwilk, miss-islington, nascheme, njs, rhettinger, serhiy.storchaka, steven.daprano, terry.reedy, xiang.zhang
Date 2018-11-30.23:10:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Given that linters like pylint can already detect the common case of this issue when using `is` and `is not` to compare to a literal where == or != seems more appropriate, I don't think a warning is very useful.

In my experience people are more likely to run code through a linter than they are to ever run an interpreter with DeprecationWarning enabled.

I do like the concept of using a not visible by default warning, but I don't think adding a LintWarning or misusing DeprecationWarning adds much value.

I suggest closing this issue as won't fix / not a bug.
Date User Action Args
2018-11-30 23:10:18gregory.p.smithsetrecipients: + gregory.p.smith, barry, nascheme, rhettinger, terry.reedy, jwilk, steven.daprano, njs, serhiy.storchaka, xiang.zhang, miss-islington
2018-11-30 23:10:18gregory.p.smithsetmessageid: <>
2018-11-30 23:10:18gregory.p.smithlinkissue34850 messages
2018-11-30 23:10:18gregory.p.smithcreate