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 AlexWaygood
Recipients AlexWaygood, FHTMitchell, JelleZijlstra, Steven Silvester, dlukes, eric.smith, graingert, gvanrossum, juliusgeo, kj, levkivskyi, python-dev, rhettinger, serhiy.storchaka, sobolevn
Date 2022-03-09.21:53:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1646862790.9.0.483895281814.issue43923@roundup.psfhosted.org>
In-reply-to
Content
I agree with Jelle — a valid protocol cannot inherit from a concrete type, and the whole point of NamedTuple is that it creates a tuple subclass (and tuple is obviously a concrete type).
History
Date User Action Args
2022-03-09 21:53:10AlexWaygoodsetrecipients: + AlexWaygood, gvanrossum, rhettinger, eric.smith, python-dev, serhiy.storchaka, graingert, levkivskyi, dlukes, JelleZijlstra, FHTMitchell, Steven Silvester, sobolevn, kj, juliusgeo
2022-03-09 21:53:10AlexWaygoodsetmessageid: <1646862790.9.0.483895281814.issue43923@roundup.psfhosted.org>
2022-03-09 21:53:10AlexWaygoodlinkissue43923 messages
2022-03-09 21:53:10AlexWaygoodcreate