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 r.david.murray
Recipients BreamoreBoy, David MacIver, Kevin Shweh, Tijs Van Oevelen, abarry, arigo, donmez, ezio.melotti, fijall, ncoghlan, r.david.murray, rhettinger, serhiy.storchaka, torsten, vstinner
Date 2015-12-14.16:52:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1450111959.2.0.87767263366.issue25843@psf.upfronthosting.co.za>
In-reply-to
Content
Ah, haypo explained the code to me, and now I understand your comment Serhiy.

So, the replacement happens because of (a) an optimizer general rule and (b) the fact that code object *can* be compared.

So it sounds like Armin's suggestion of making an exception for code objects in the optimizer is the correct solution.

The issue with code objects that aren't really equal comparing equal would then be a separate bug that affects, as Serhiy said, only testing (that we know of...who knows what people like PJE might be doing with comparing code objects :)
History
Date User Action Args
2015-12-14 16:52:39r.david.murraysetrecipients: + r.david.murray, arigo, rhettinger, ncoghlan, vstinner, donmez, ezio.melotti, torsten, BreamoreBoy, fijall, serhiy.storchaka, David MacIver, abarry, Kevin Shweh, Tijs Van Oevelen
2015-12-14 16:52:39r.david.murraysetmessageid: <1450111959.2.0.87767263366.issue25843@psf.upfronthosting.co.za>
2015-12-14 16:52:39r.david.murraylinkissue25843 messages
2015-12-14 16:52:38r.david.murraycreate