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 kj
Recipients BvB93, JelleZijlstra, farcat, gvanrossum, kj, lars2, lukasz.langa, miss-islington, pablogsal, serhiy.storchaka, uriyyo
Date 2021-08-19.17:50:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Now a subclass of an Annotated alias is a generic type. Should it be?

I'm unsure if Annotated should be subclassable in the first place, but if I understand PEP 593 correctly,
class X(Annotated[int, (1, 10)]), should be equivalent to class X(int) right? If that's the case, it's subclassable and Generic shouldn't be in the MRO.

FWIW, the other special forms don't allow subclassing, so we don't need to think about this problem for them. Annotated is a special cookie.

I propose we just drop the _name hack temporarily in Annotated. A real fix requires fixing up __mro_entries__, but I am uncomfortable with us backporting to 3.10 anything that touches __mro_entries__ due to the numerous edge cases it has and how close we are to 3.10 final.
Date User Action Args
2021-08-19 17:50:08kjsetrecipients: + kj, gvanrossum, farcat, lukasz.langa, serhiy.storchaka, JelleZijlstra, pablogsal, miss-islington, uriyyo, BvB93, lars2
2021-08-19 17:50:08kjsetmessageid: <>
2021-08-19 17:50:08kjlinkissue44524 messages
2021-08-19 17:50:08kjcreate