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 methane
Recipients JelleZijlstra, eric.smith, giampaolo.rodola, gvanrossum, lazka, llllllllll, methane, ncoghlan, pitrou, rhettinger, serhiy.storchaka, vstinner, xiang.zhang
Date 2017-07-19.08:00:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I want to focus on pure Python implementation in this issue.

While "40x faster" is more 10x faster than "4x faster", C implementation
can boost only CPython and makes maintenance more harder.

And sometimes "more 10x faster" is not so important.
For example, say application startup takes 1sec and namedtuple
creation took 0.4sec of the 1sec:

  4x faster: 1sec -> 0.7sec  (-30%)
 40x faster: 1sec -> 0.61sec (-39%)

In this case, "4x faster" reduces 0.3sec and "more 10x faster" reduces
only 0.09sec.

Of course, 1.9x faster attribute access ( is attractive.
But this issue is too long already.
Date User Action Args
2017-07-19 08:00:23methanesetrecipients: + methane, gvanrossum, rhettinger, ncoghlan, pitrou, vstinner, eric.smith, giampaolo.rodola, serhiy.storchaka, llllllllll, xiang.zhang, JelleZijlstra, lazka
2017-07-19 08:00:23methanesetmessageid: <>
2017-07-19 08:00:23methanelinkissue28638 messages
2017-07-19 08:00:23methanecreate