➜

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 JelleZijlstra
Recipients JelleZijlstra, eric.smith, giampaolo.rodola, gvanrossum, lazka, llllllllll, methane, ncoghlan, pitrou, rhettinger, serhiy.storchaka, vstinner, xiang.zhang
Date 2017-07-19.05:39:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1500442787.58.0.538233281427.issue28638@psf.upfronthosting.co.za>
In-reply-to
Content 
Thanks Joe! I adapted your benchmark suite to also run my implementation. See https://github.com/JelleZijlstra/cnamedtuple/commit/61b6fbf4de37f8131ab43c619593327004974e52 for the code and results. The results are consistent with what we've seen before.

Joe's cnamedtuple is about 40x faster for class creation than the current implementation, and my PR only speeds class creation up by 4x. That difference is big enough that I think we should seriously consider using the C implementation.
History
Date User Action Args
2017-07-19 05:39:47JelleZijlstrasetrecipients: + JelleZijlstra, gvanrossum, rhettinger, ncoghlan, pitrou, vstinner, eric.smith, giampaolo.rodola, methane, serhiy.storchaka, llllllllll, xiang.zhang, lazka
2017-07-19 05:39:47JelleZijlstrasetmessageid: <1500442787.58.0.538233281427.issue28638@psf.upfronthosting.co.za>
2017-07-19 05:39:47JelleZijlstralinkissue28638 messages
2017-07-19 05:39:47JelleZijlstracreate