[issue19640] Dynamically generate the _source attribute of namedtuple to save memory)

Raymond Hettinger report at bugs.python.org
Wed Apr 2 22:28:04 CEST 2014


Raymond Hettinger added the comment:

Victor, I don't think the added complexity is worth 2k per named tuple class.  Every time I've gone down the path of lazy evaluation, I've paid an unexpected price for it down the road.  If the savings were huge, it might be worth it, but that isn't the case here.  This isn't really different than proposing that all docstring be in a separate module to be lazily loaded only when people look at help.

----------
resolution:  -> rejected
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19640>
_______________________________________


More information about the Python-bugs-list mailing list