➜

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 JelleZijlstra
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:27:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1646861226.72.0.793578888881.issue43923@roundup.psfhosted.org>
In-reply-to
Content 
A NamedTuple that is also a Protocol doesn't make sense to me, since a NamedTuple is a concrete (nominal) type and a Protocol cannot inherit from a concrete type. If you want something like that to happen, it's better to open an issue on https://github.com/python/typing first, so this issue can stay focused on support for Generic + NamedTuple.
History
Date User Action Args
2022-03-09 21:27:07JelleZijlstrasetrecipients: + JelleZijlstra, gvanrossum, rhettinger, eric.smith, python-dev, serhiy.storchaka, graingert, levkivskyi, dlukes, FHTMitchell, Steven Silvester, sobolevn, kj, AlexWaygood, juliusgeo
2022-03-09 21:27:06JelleZijlstrasetmessageid: <1646861226.72.0.793578888881.issue43923@roundup.psfhosted.org>
2022-03-09 21:27:06JelleZijlstralinkissue43923 messages
2022-03-09 21:27:06JelleZijlstracreate