➜

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 gvanrossum
Recipients AlexWaygood, FHTMitchell, JelleZijlstra, Steven Silvester, dlukes, eric.smith, graingert, gvanrossum, kj, levkivskyi, python-dev, rhettinger, serhiy.storchaka, sobolevn
Date 2022-03-08.00:37:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1646699862.89.0.661318357028.issue43923@roundup.psfhosted.org>
In-reply-to
Content 
Playing tricks where compile-time and run-time see slightly different types is probably more productive than trying to revert a PR that was in Python 3.9 and 3.10. :-)

I'm not opposed to supporting generic NamedTuple, but I expect the fix will never hit 3.9 and 3.10, and it needs to be a "fix forward" PR.

Would you mind closing the "revert" PR unmerged?
History
Date User Action Args
2022-03-08 00:37:43gvanrossumsetrecipients: + gvanrossum, rhettinger, eric.smith, python-dev, serhiy.storchaka, graingert, levkivskyi, dlukes, JelleZijlstra, FHTMitchell, Steven Silvester, sobolevn, kj, AlexWaygood
2022-03-08 00:37:42gvanrossumsetmessageid: <1646699862.89.0.661318357028.issue43923@roundup.psfhosted.org>
2022-03-08 00:37:42gvanrossumlinkissue43923 messages
2022-03-08 00:37:42gvanrossumcreate