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 jtaylor
Recipients Mark.Shannon, jtaylor, lemburg, pitrou, rhettinger, scoder, serhiy.storchaka, tim.peters
Date 2015-07-10.07:32:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Your benchmarks are not affected by this change see the other issue. They are also not representative of every workload out there.

I can at least see the argument why you didn't want to put the other variant of this change in as it made the code a tiny bit more complicated, but I do not understand the reluctance for this variant. It doesn't change the complexity of the code one bit.
If you doubt the performance of pythons own small object allocator, python should maybe stop using it alltogether?
Date User Action Args
2015-07-10 07:32:49jtaylorsetrecipients: + jtaylor, lemburg, tim.peters, rhettinger, pitrou, scoder, Mark.Shannon, serhiy.storchaka
2015-07-10 07:32:49jtaylorsetmessageid: <>
2015-07-10 07:32:49jtaylorlinkissue23601 messages
2015-07-10 07:32:48jtaylorcreate