➜

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 Stefan Pochmann
Recipients Stefan Pochmann, rhettinger, tim.peters
Date 2021-10-20.05:29:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1634707795.8.0.583820033559.issue45530@roundup.psfhosted.org>
In-reply-to
Content 
I misinterpreted you then, sorry. I guess also because Elliot shortly after retrated from the approach, saying he "rewrote unsafe_tuple_compare to move the less-than after the equality testing, to make sure it's 100% consistent".

I'd say the inconsistency the program showed was different. Yes, the xs got sorted differently than the ys, but the xs differed from the ys. The proposed method would change comparisons of *the same* tuples. You'd for example no longer have "sorted(tuples) == [min(tuples), max(tuples)]" for a list of two tuples.

Also curious factoid: I recently saw a case where despite the "only <" promise, sorting caused an "x > y" comparison (because "y < x" wasn't implemented).

(tiny note: tupsort.py does "range(2", should be "range(1" I think)
History
Date User Action Args
2021-10-20 05:29:55Stefan Pochmannsetrecipients: + Stefan Pochmann, tim.peters, rhettinger
2021-10-20 05:29:55Stefan Pochmannsetmessageid: <1634707795.8.0.583820033559.issue45530@roundup.psfhosted.org>
2021-10-20 05:29:55Stefan Pochmannlinkissue45530 messages
2021-10-20 05:29:55Stefan Pochmanncreate