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 gvanrossum, levkivskyi, serhiy.storchaka
Date 2020-04-04.21:08:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
typing.NamedTuple is used in two ways.

1. It is a callable which produces a new namedtuple type.
2. It can also be used as a base in the class statement for creating a new namedtuple type.

In both cases it is not a real class. You cannot create an instance of NamedTuple or a subclass of NamedTuple. But it is implemented as a class, and help() shows methods and data descriptors for it, which are useless.

The proposed PR implements NamedTuple like a function. Implementation of the __mro_entries__ method allows to use it as a base in the class statement.
Date User Action Args
2020-04-04 21:08:45serhiy.storchakasetrecipients: + serhiy.storchaka, gvanrossum, levkivskyi
2020-04-04 21:08:45serhiy.storchakasetmessageid: <>
2020-04-04 21:08:45serhiy.storchakalinkissue40185 messages
2020-04-04 21:08:44serhiy.storchakacreate