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 vstinner
Recipients JelleZijlstra, eric.smith, giampaolo.rodola, gvanrossum, lazka, llllllllll, methane, ncoghlan, pitrou, rhettinger, serhiy.storchaka, vstinner, xiang.zhang
Date 2017-07-19.11:34:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1500464055.41.0.0637991660718.issue28638@psf.upfronthosting.co.za>
In-reply-to
Content
General note about this issue: while the issie title is "Optimize namedtuple creation", it would be *nice* to not only optimization the creation but also attribute access by name:
http://bugs.python.org/issue28638#msg298499

Maybe we can have a very fast C implementation using structseq, and a fast Python implementation (faster than the current Python implementation) fallback for non-CPython.
History
Date User Action Args
2017-07-19 11:34:15vstinnersetrecipients: + vstinner, gvanrossum, rhettinger, ncoghlan, pitrou, eric.smith, giampaolo.rodola, methane, serhiy.storchaka, llllllllll, xiang.zhang, JelleZijlstra, lazka
2017-07-19 11:34:15vstinnersetmessageid: <1500464055.41.0.0637991660718.issue28638@psf.upfronthosting.co.za>
2017-07-19 11:34:15vstinnerlinkissue28638 messages
2017-07-19 11:34:15vstinnercreate