Raymond Hettinger <rhettin...@users.sourceforge.net> added the comment:
Sorry, this was by design. There were two possible constructors, one using positional arguments or keywords and one from an iterable. Either one could have been the main constructor. A number of use cases favored the one that we choose. It was a good decision, but not a perfect one. To construct a namedtuple directly from an existing tuple, either use: ntuple(*t) or ntuple._make(t) The class is functioning as designed, documented, and tested. There is no way to change it without breaking most existing uses. Closing as rejected. ---------- assignee: -> rhettinger resolution: -> rejected status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8415> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
