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 steven.daprano
Recipients barry, gregory.p.smith, jwilk, miss-islington, nascheme, njs, rhettinger, serhiy.storchaka, steven.daprano, terry.reedy, xiang.zhang
Date 2018-12-01.00:59:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Looks like we have a stand-off between core devs, and no BDFL to make a ruling.

There is support for the feature from at least Barry and Raymond  (although I think Guido was cool on the idea, maybe?). Gregory, do you feel strongly enough about this that you would reverse the commit if Serhiy just went ahead and committed it? Nobody wants a revert war :-)

To me, this seems like a low-cost feature that will help some developers without inconveniencing anyone. As Serhiy points out, SyntaxWarning is only emitted when the code is compiled, so it is only going to be visible to the developer of the module, not the user of the module.

Let's not allow the perfect be the enemy of the good enough. I think this is a helpful feature for developers, and as Raymond says it will help teach beginners the difference between `is` and equality. The people who are most prone to making this mistake are the ones least likely to be using a linter. And we know it is helpful: Serhiy already used it to find a bug in IDLE.

Gregory, you wanted to close this as not a bug, but nobody says it is a bug, it is an enhancement. And I think there is consensus that this *is* an enhancement. Nobody has said that there are good use cases for using `is` on literals in production code.
Date User Action Args
2018-12-01 00:59:29steven.dapranosetrecipients: + steven.daprano, barry, nascheme, rhettinger, terry.reedy, gregory.p.smith, jwilk, njs, serhiy.storchaka, xiang.zhang, miss-islington
2018-12-01 00:59:28steven.dapranosetmessageid: <>
2018-12-01 00:59:28steven.dapranolinkissue34850 messages
2018-12-01 00:59:27steven.dapranocreate