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 tim.peters
Recipients Marco Sulla, brandtbucher, cheryl.sabella, mark.dickinson, rhettinger, serhiy.storchaka, tim.peters
Date 2019-12-15.20:20:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1576441251.56.0.820517922298.issue36095@roundup.psfhosted.org>
In-reply-to
Content
Closing as Mark suggested, but as "not a bug" rather than "won't fix".  That floats aren't totally ordered is a consequence of IEEE 754 semantics, not Python's whim.  As Mark said, if people want a total_ordering function for floats, that should be opened as a different issue - we're not going to change the default float comparison logic.
History
Date User Action Args
2019-12-15 20:20:51tim.peterssetrecipients: + tim.peters, rhettinger, mark.dickinson, serhiy.storchaka, cheryl.sabella, brandtbucher, Marco Sulla
2019-12-15 20:20:51tim.peterssetmessageid: <1576441251.56.0.820517922298.issue36095@roundup.psfhosted.org>
2019-12-15 20:20:51tim.peterslinkissue36095 messages
2019-12-15 20:20:51tim.peterscreate