How to handle type checking for pybind11 enum types

[mhall-altair]

I'm running into an issue where I'm attempting to use mypy's strict-equality check but certain errors are being missed due to how pybind11 handles enum classes. This seems to be a known issue, that pybind11 produces enum classes that do not derive from Python's enum.Enum class.

An example of the stubs generated by pybind11-stubgen (version 2.5.1) are here:

class MYENUM_TYPE:
    """
    Members:
    
      MYENUM_ONE
   
      MYENUM_TWO
    """
    MYENUM_ONE: typing.ClassVar[MYENUM_TYPE]  # value = <DATA_TYPE.MYENUM_ONE: 0>
    MYENUM_TWO: typing.ClassVar[MYENUM_TYPE]  # value = <DATA_TYPE.MYENUM_TWO: 1>
    __members__: typing.ClassVar[Dict[str, MYENUM_TYPE]]  # value = {'MYENUM_ONE': <DATA_TYPE.MYENUM_ONE: 0>, 'MYENUM_TWO': <DATA_TYPE.MYENUM_TWO: 1>}
    def __eq__(self, other: typing.Any) -> bool: ...
    def __getstate__(self) -> int: ...
    def __hash__(self) -> int: ...
    def __index__(self) -> int: ...
    def __init__(self, value: int) -> None: ...
    def __int__(self) -> int: ...
    def __ne__(self, other: typing.Any) -> bool: ...
    def __repr__(self) -> str: ...
    def __setstate__(self, state: int) -> None: ...
    def __str__(self) -> str: ...
    @property
    def name(self) -> str: ...
    @property
    def value(self) -> int: ...

Since these classes are not derived from enum.Enum and define a __eq__ method, mypy skips any overlapping equality checks. This allows for code like MYENUM_TYPE.MYENUM_ONE == "Foo" to pass mypy. My current workaround is to just remove the __eq__ methods from my stub files.

Does anyone know of a better way to handle these stubs in a type checking scenario?