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, gvanrossum, miss-islington, njs, serhiy.storchaka, steven.daprano, terry.reedy, xiang.zhang
Date 2018-10-01.01:39:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
If we were to ship a "chaos" mode in the CPython interpreter itself, I assume you envision an interpreter flag and/or env var?  If it required someone compiling the interpreter a special way I don't think it would be widely adopted within continuous integration testing systems.

I was actually pondering doing a "chaos" mode of sorts at work because I have the power to cause everyone's tests to be run that way mode by default.  (I'd basically just disable interning and str/int singletons)  But while it's a nice idea, it's low on my work priorities.  While we had thousands of is literal comparisons that we're about to fix en-masse, they are only a tiny fraction of all literal comparisons in our codebase.  And pylint is now more widely used which should help prevent new ones.
Date User Action Args
2018-10-01 01:39:37gregory.p.smithsetrecipients: + gregory.p.smith, gvanrossum, barry, terry.reedy, steven.daprano, njs, serhiy.storchaka, xiang.zhang, miss-islington
2018-10-01 01:39:36gregory.p.smithsetmessageid: <>
2018-10-01 01:39:36gregory.p.smithlinkissue34850 messages
2018-10-01 01:39:35gregory.p.smithcreate