[issue33298] Wrap only constants with _PyCode_ConstantKey() in the compiler.

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ _

[issue33298] Wrap only constants with _PyCode_ConstantKey() in the compiler.

Serhiy Storchaka added the comment: New changeset d70c2a6894d80410b6f5a3129d6b1062ea8fd4e4 by Serhiy Storchaka in branch 'master': bpo-33298: Wrap only constants with _PyCode_ConstantKey() in the compiler. (GH-6512) https://github.com/python/cpython/commit/d70c2a6894d80410b6f5a3129d6b1062ea8f

[issue33298] Wrap only constants with _PyCode_ConstantKey() in the compiler.

Change by INADA Naoki : -- nosy: +inada.naoki ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyt

[issue33298] Wrap only constants with _PyCode_ConstantKey() in the compiler.

Serhiy Storchaka added the comment: See issue33299 for the first option. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue33298] Wrap only constants with _PyCode_ConstantKey() in the compiler.

Change by Serhiy Storchaka : -- nosy: +vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue33298] Wrap only constants with _PyCode_ConstantKey() in the compiler.

Change by Serhiy Storchaka : -- keywords: +patch pull_requests: +6205 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-

[issue33298] Wrap only constants with _PyCode_ConstantKey() in the compiler.

New submission from Serhiy Storchaka : Currently every constant is wrapped with _PyCode_ConstantKey() in the compiler. This is necessary for distinguishing numbers 1, 1.0 and 1.0+0j, 0.0 and -0.0, and avoiding warnings from comparing string and bytes constants. But the change that introduced u