Author Jelle Zijlstra
Recipients Jelle Zijlstra, eric.smith, inada.naoki, ncoghlan, rhettinger, serhiy.storchaka, xiang.zhang
Date 2017-07-15.17:58:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1500141529.11.0.503800557643.issue28638@psf.upfronthosting.co.za>
In-reply-to
Content
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 https://github.com/JelleZijlstra/cpython/commit/5634af4ccfd06a2fabc2cc2cfcc9c014caf6f389 and found that it speeds up namedtuple creation, uses less code, and creates only one necessary backwards compatibility break (we no longer have _source).
History
Date User Action Args
2017-07-15 17:58:49Jelle Zijlstrasetrecipients: + Jelle Zijlstra, rhettinger, ncoghlan, eric.smith, inada.naoki, serhiy.storchaka, xiang.zhang
2017-07-15 17:58:49Jelle Zijlstrasetmessageid: <1500141529.11.0.503800557643.issue28638@psf.upfronthosting.co.za>
2017-07-15 17:58:49Jelle Zijlstralinkissue28638 messages
2017-07-15 17:58:48Jelle Zijlstracreate