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 elliot.gorokhovsky, mdk, ppperry, serhiy.storchaka, tim.peters, vstinner
Date 2017-03-12.04:01:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Elliot, I don't care if the example behaves differently.  Although someone else may ;-)

The only things `.sort()` has ever tried to guarantee in the presence of mutations (of either the list or the elements) during sorting are that (a) the implementation won't segfault; and, (b) the list at the end is _some_ permutation of the input list (no elements are lost or duplicated).

If crazy mutation examples can provoke a segfault, that's possibly "a problem" - but different results really aren't (at least not to me).
Date User Action Args
2017-03-12 04:01:18tim.peterssetrecipients: + tim.peters, vstinner, serhiy.storchaka, ppperry, mdk, elliot.gorokhovsky
2017-03-12 04:01:18tim.peterssetmessageid: <>
2017-03-12 04:01:17tim.peterslinkissue28685 messages
2017-03-12 04:01:17tim.peterscreate