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 alexandre.vassalotti
Recipients alexandre.vassalotti, jcea, pitrou, serhiy.storchaka
Date 2013-04-07.19:15:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1365362127.5.0.0370956886956.issue16551@psf.upfronthosting.co.za>
In-reply-to
Content
My point is I would prefer that we keep all optimizations to only the _pickle C module and keep the Python implementation as simple as possible.

Also, I doubt the slight speedup shown by your microbenchmark will actually result in any significant benefits on the overall performance of pickle.py. Furthermore, we can't use CPython to measure the benefits of such optimization because CPython will always use _pickle over the Python implementation.
History
Date User Action Args
2013-04-07 19:15:27alexandre.vassalottisetrecipients: + alexandre.vassalotti, jcea, pitrou, serhiy.storchaka
2013-04-07 19:15:27alexandre.vassalottisetmessageid: <1365362127.5.0.0370956886956.issue16551@psf.upfronthosting.co.za>
2013-04-07 19:15:27alexandre.vassalottilinkissue16551 messages
2013-04-07 19:15:27alexandre.vassalotticreate