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 rhettinger
Recipients NeilGirdhar, alexdelorenzo, eric.smith, levkivskyi, rhettinger
Date 2018-08-10.18:40:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1533926452.47.0.56676864532.issue34363@psf.upfronthosting.co.za>
In-reply-to
Content
> Raymond has resisted adding a base class to namedtuple. I believe the
> preferred way to identify a namedtuple is to look for a _fields member.

FWIW, that was also Guido's opinion as well.  A named tuple is generic concept defined in the glossary as "Any tuple-like class whose indexable elements are also accessible using a named attribute".  This includes user-defined classes, classes created by collections.namedtuple, and instances of structseq.  The code generated by oollections.namedtuple was based on patterns already in widespread use at the time.
History
Date User Action Args
2018-08-10 18:40:52rhettingersetrecipients: + rhettinger, eric.smith, NeilGirdhar, levkivskyi, alexdelorenzo
2018-08-10 18:40:52rhettingersetmessageid: <1533926452.47.0.56676864532.issue34363@psf.upfronthosting.co.za>
2018-08-10 18:40:52rhettingerlinkissue34363 messages
2018-08-10 18:40:52rhettingercreate