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 mdk
Recipients Mariatta, dfrojas, eli.bendersky, lukasz.langa, matrixise, mdk, nedbat, rhettinger, scoder, serhiy.storchaka, sivert, taleinat, vstinner
Date 2019-03-18.22:57:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
We found two occurrences of external code breaking due to this change, and one looks tricky to fix (docutils), this indicates there are other library that will break.

> My (somewhat educated) gut feeling is that most users simply won't care or won't even notice the change.

I concur with this. Why changing the default behavior? The costs of changing this looks high, and the benefits looks very low (people not noticing).

As already proposed, a keyword-only `sorted` parameter defaulting to True (the current behavior) would allow one to give False and get control of ordering, and won't break any existing library.

On the plus side `sorted=True` makes the current behavior (sorted by default) more discoverable.
Date User Action Args
2019-03-18 22:57:08mdksetrecipients: + mdk, rhettinger, scoder, vstinner, taleinat, nedbat, eli.bendersky, lukasz.langa, serhiy.storchaka, matrixise, sivert, Mariatta, dfrojas
2019-03-18 22:57:07mdksetmessageid: <>
2019-03-18 22:57:07mdklinkissue34160 messages
2019-03-18 22:57:07mdkcreate