➜

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 abarry
Recipients David MacIver, Kevin Shweh, Tijs Van Oevelen, abarry, arigo, donmez, ezio.melotti, fijall, ncoghlan, r.david.murray, rhettinger, serhiy.storchaka, torsten
Date 2015-12-13.19:40:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1450035615.8.0.713737187314.issue25843@psf.upfronthosting.co.za>
In-reply-to
Content 
I'm not suggesting to get rid of the rich compare ability of code objects, which makes sense to me. What doesn't make sense to me, however, is when a function's code object is replaced by another one because it compares equal. I see no use case for this, and only leads to head-scratching.

I believe code objects should not be touched at all.
History
Date User Action Args
2015-12-13 19:40:15abarrysetrecipients: + abarry, arigo, rhettinger, ncoghlan, donmez, ezio.melotti, r.david.murray, torsten, fijall, serhiy.storchaka, David MacIver, Kevin Shweh, Tijs Van Oevelen
2015-12-13 19:40:15abarrysetmessageid: <1450035615.8.0.713737187314.issue25843@psf.upfronthosting.co.za>
2015-12-13 19:40:15abarrylinkissue25843 messages
2015-12-13 19:40:15abarrycreate