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 rhettinger
Recipients daniel.urban, eric.smith, gruszczy, ncoghlan, rhettinger, stutzbach, terry.reedy
Date 2011-04-04.18:05:32
SpamBayes Score 3.8427974e-08
Marked as misclassified No
Message-id <1301940333.87.0.622869741116.issue11707@psf.upfronthosting.co.za>
In-reply-to
Content
I was only aiming for Py3.3.  

If someone wanted to push for a backport to 3.2, it would be up to the release manager to decide whether a performance booster would be worth the risk of introducing a bug in a point release.

ISTM that if someone really cared about performance, they would probably already be using an O(n) key-function approach.  This patch eliminates most of the overhead for calling a cmp-function, but it can't do anything about the body of the user-supplied cmp-function which will dominate the running time if it does anything useful.
History
Date User Action Args
2011-04-04 18:05:33rhettingersetrecipients: + rhettinger, terry.reedy, ncoghlan, eric.smith, stutzbach, gruszczy, daniel.urban
2011-04-04 18:05:33rhettingersetmessageid: <1301940333.87.0.622869741116.issue11707@psf.upfronthosting.co.za>
2011-04-04 18:05:32rhettingerlinkissue11707 messages
2011-04-04 18:05:32rhettingercreate