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 serhiy.storchaka
Recipients methane, ncoghlan, rhettinger, serhiy.storchaka, xiang.zhang
Date 2016-11-08.11:17:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Using namedtuple is not new in 3.6, thus this is not a regression that can be fixed at beta stage.

Inlining the source of a named tuple class looks ugly solution. It would be better to write the source in separate file and import it. Makefile can have a rule for recreating this source file if is changed.

More general solution would be to make namedtuple() using cached precompiled class and update the cache if it doesn't match namedtuple arguments.

Yet one solution is to make namedtuple() not using compiling, but return patched local class. But Raymond is against this.
Date User Action Args
2016-11-08 11:17:32serhiy.storchakasetrecipients: + serhiy.storchaka, rhettinger, ncoghlan, methane, xiang.zhang
2016-11-08 11:17:32serhiy.storchakasetmessageid: <>
2016-11-08 11:17:32serhiy.storchakalinkissue28638 messages
2016-11-08 11:17:32serhiy.storchakacreate