Message338296
| 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 | <1552949827.99.0.408597117871.issue34160@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
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. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-03-18 22:57:08 | mdk | set | recipients: + mdk, rhettinger, scoder, vstinner, taleinat, nedbat, eli.bendersky, lukasz.langa, serhiy.storchaka, matrixise, sivert, Mariatta, dfrojas |
| 2019-03-18 22:57:07 | mdk | set | messageid: <1552949827.99.0.408597117871.issue34160@roundup.psfhosted.org> |
| 2019-03-18 22:57:07 | mdk | link | issue34160 messages |
| 2019-03-18 22:57:07 | mdk | create | |