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 eric.smith, methane, ncoghlan, rhettinger, serhiy.storchaka, xiang.zhang
Date 2016-12-05.10:48:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I think external cache system introduces more complexity and startup overhead than AC.

I think functools is the only "very common" module using namedtuple, because
`functools.wraps()` is used to create decorator functions.

But if general solution for all namedtuple is necessary to make agreement,
I think C implemented namedtuple may be better.
structseq is faster than namedtuple, not only when building type, but also
using instance.

$ ./python -m perf timeit -s 'import sys; vi = sys.version_info' -- 'vi.major, vi.minor, vi.micro'
Median +- std dev: 130 ns +- 2 ns

$ ./python -m perf timeit -s 'from collections import namedtuple; VersionInfo=namedtuple("VersionInfo", "major minor micro releaselevel serial"); vi=VersionInfo(3, 7, 0, "alpha", 0)' -- 'vi.major, vi.minor, vi.micro'
Median +- std dev: 212 ns +- 4 ns
Date User Action Args
2016-12-05 10:48:19methanesetrecipients: + methane, rhettinger, ncoghlan, eric.smith, serhiy.storchaka, xiang.zhang
2016-12-05 10:48:19methanesetmessageid: <>
2016-12-05 10:48:19methanelinkissue28638 messages
2016-12-05 10:48:19methanecreate