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 LLyaudet, brandtbucher, erlendaasland, koos.zevenhoven, tim.peters, vincent.juge, xtreak
Date 2021-09-01.19:43:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I created a PR that implements the powersort merge strategy:

Across all the time this issue report has been open, that strategy continues to be the top contender. Enough already ;-) It's indeed a more difficult change to make to the code, but that's in relative terms. In absolute terms, it's not at all a hard change.

Laurent, if you find that some variant of ShiversSort actually runs faster than that, let us know here! I'm a big fan of Vincent's innovations too, but powersort seems to do somewhat better "on average" than even his length-adaptive ShiversSort (and implementing that too would require changing code outside of merge_collapse()).
Date User Action Args
2021-09-01 19:43:23tim.peterssetrecipients: + tim.peters, koos.zevenhoven, xtreak, brandtbucher, vincent.juge, erlendaasland, LLyaudet
2021-09-01 19:43:23tim.peterssetmessageid: <>
2021-09-01 19:43:23tim.peterslinkissue34561 messages
2021-09-01 19:43:23tim.peterscreate