Message256318
> The lowest impact fix from a code change would be to add a type equivalence check for constants as Raymond first suggested, as that only involves adding an extra check to code_richcompare: https://hg.python.org/cpython/file/tip/Objects/codeobject.c#l416
It is not so easy. (1,) and (1.0,) are equal and have the same type. To make correct type-sensitive equivalence check, you need to introduce new protocol, new special method on low level and new operator/function on high level. |
|
Date |
User |
Action |
Args |
2015-12-13 08:54:12 | serhiy.storchaka | set | recipients:
+ serhiy.storchaka, arigo, rhettinger, ncoghlan, donmez, ezio.melotti, r.david.murray, torsten, fijall, Kevin Shweh, Tijs Van Oevelen |
2015-12-13 08:54:12 | serhiy.storchaka | set | messageid: <1449996852.68.0.870204393501.issue25843@psf.upfronthosting.co.za> |
2015-12-13 08:54:12 | serhiy.storchaka | link | issue25843 messages |
2015-12-13 08:54:12 | serhiy.storchaka | create | |
|