Mypy does not like this change:

stdlib/typing.pyi:865: error: Metaclass conflict: the metaclass of a derived class must be a (non-strict) subclass of the metaclasses of all its bases

I think the reason is that tuple inherits types that use ABCMeta, so, let's preted that NamedTupleMeta also has ABCMeta.

Now pyright finds some cases where NamedTuple is used together with Enum:

class _ASN1ObjectBase(NamedTuple):
    nid: int
    shortname: str
    longname: str
    oid: str

class _ASN1Object(_ASN1ObjectBase):
    def __new__(cls, oid: str) -> Self: ...
    @classmethod
    def fromnid(cls, nid: int) -> Self: ...
    @classmethod
    def fromname(cls, name: str) -> Self: ...

class Purpose(_ASN1Object, enum.Enum):
    SERVER_AUTH: _ASN1Object
    CLIENT_AUTH: _ASN1Object

Another option for us is to use # type: ignore[misc] on this definition. I will give this a try.

:(

According to mypy_primer, this change has no effect on the checked open source code. 🤖🎉

Sorry, seems like this didn't work out. The linked mypy bug should likely be fixed with special-casing in mypy itself.