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 larry
Recipients David MacIver, Kevin Shweh, Tijs Van Oevelen, abarry, arigo, donmez, ezio.melotti, fijall, larry, mark.dickinson, ncoghlan, python-dev, r.david.murray, rhettinger, serhiy.storchaka, torsten, vstinner
Date 2016-06-14.12:53:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Someone asked on reddit.  The Misc/NEWS entry for this reads:

Issue #25843: When compiling code, don’t merge constants if they are equal but have a different types. For example, f1, f2 = lambda: 1, lambda: 1.0 is now correctly compiled to two different functions: f1() returns 1 (int) and f2() returns 1.0 (int), even if 1 and 1.0 are equal.

Shouldn't that last part read
"and f2() returns 1.0 (float), even if 1 and 1.0 are equal."

As in, f2 returns a float, not an int.

If this is a mistake, let me fix it for 3.5.2 final and I'll merge it back into trunk etc.  If you fix it it wouldn't ship in 3.5.2 final.
Date User Action Args
2016-06-14 12:53:48larrysetrecipients: + larry, arigo, rhettinger, mark.dickinson, ncoghlan, vstinner, donmez, ezio.melotti, r.david.murray, torsten, fijall, python-dev, serhiy.storchaka, David MacIver, abarry, Kevin Shweh, Tijs Van Oevelen
2016-06-14 12:53:48larrysetmessageid: <>
2016-06-14 12:53:48larrylinkissue25843 messages
2016-06-14 12:53:47larrycreate