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, methane, ncoghlan, rhettinger, serhiy.storchaka, xiang.zhang
Date 2017-07-15.17:58:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I'm also concerned that the slowness of namedtuple creation is causing people to avoid using it. I can see why we wouldn't want a complicated solution like using Argument Clinic, but it's not clear to me why Serhiy's approach in namedtuple-no-compile.patch was rejected. This approach could provide a speedup for all namedtuple instantiations without complicating the implementation. I wrote a similar implementation in and found that it speeds up namedtuple creation, uses less code, and creates only one necessary backwards compatibility break (we no longer have _source).
Date User Action Args
2017-07-15 17:58:49JelleZijlstrasetrecipients: + JelleZijlstra, rhettinger, ncoghlan, eric.smith, methane, serhiy.storchaka, xiang.zhang
2017-07-15 17:58:49JelleZijlstrasetmessageid: <>
2017-07-15 17:58:49JelleZijlstralinkissue28638 messages
2017-07-15 17:58:48JelleZijlstracreate