Julian Taylor added the comment: 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? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue23601> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
