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 eric.smith
Recipients NeilGirdhar, alexdelorenzo, eric.smith, levkivskyi
Date 2018-08-10.18:30:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Hmm, for some reason I'm not getting mail from this issue, so I made my PR before I saw the comments since my last comment.

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. We could do that instead of use the (*[]) trick for all classes derived from tuple or list.

Maybe it's worthwhile bringing up the differences in how tuple and namedtuple handle creation with iterables on python-dev.

I'm still not certain of the right approach, but PR 8728 adds some tests and fixes the problem identified in this issue. I probably won't commit it until I can discuss with some other people.
Date User Action Args
2018-08-10 18:30:29eric.smithsetrecipients: + eric.smith, NeilGirdhar, levkivskyi, alexdelorenzo
2018-08-10 18:30:29eric.smithsetmessageid: <>
2018-08-10 18:30:29eric.smithlinkissue34363 messages
2018-08-10 18:30:29eric.smithcreate