Serhiy Storchaka added the comment: 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 collections.py 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. ---------- assignee: -> rhettinger versions: -Python 3.6 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28638> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
