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 scoder
Recipients Mark.Shannon, jtaylor, lemburg, pitrou, rhettinger, scoder, serhiy.storchaka, tim.peters
Date 2015-07-10.17:26:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
> Your benchmarks are not affected by this change see the other issue.

Then you ran them, I assume? Could you show the output here that you got?

> They are also not representative of every workload out there.

Certainly not, but they do provide a certain variety of workloads that
reduce the likelihood of not spotting a regression that this change might

Note that people seem to be rather in favour of your proposed change. If
you can show that there are no visible drawbacks, one of them will most
likely apply it for you.
Date User Action Args
2015-07-10 17:26:56scodersetrecipients: + scoder, lemburg, tim.peters, rhettinger, pitrou, Mark.Shannon, jtaylor, serhiy.storchaka
2015-07-10 17:26:56scoderlinkissue23601 messages
2015-07-10 17:26:56scodercreate