Enum member annotations mask subclass in type annotation resolution

[PikalaxALT]

The way enum stubs are defined causes their values to appear to PyCharm as their annotated type rather than as instances of their class. This causes PyCharm to warn that, for example, the per= argument to commands.MaxConcurrency.__init__ is an int rather than the expected BucketType.

[bryanforbes]

This seems like a PyCharm issue as the stubs are using the standard enum.Enum class as the base class for all of the enums in discord. I'd be interested to see what PyCharm does with the following code:

from enum import Enum

class MyEnum(Enum):
    One = 1
    Two = 2

def my_function(arg: MyEnum) -> None:
    pass

my_function(MyEnum.One)

[Gobot1234]

AFAIK PyCharm takes the annotated value to be the correct one ignoring the fact it's in an Enum, that code therefore runs fine.

[bryanforbes]

AFAIK PyCharm takes the annotated value to be the correct one ignoring the fact it's in an Enum, that code therefore runs fine.

Then I'm not sure why PyCharm would have an issue with BucketType since it's done exactly the same way.

[Gobot1234]

I've tried doing this in stubs before, the only way to get it to work is to type hint members as instances of the enum.

[bryanforbes]

My whole point is that this works fine in mypy and, (as far as I can tell) according to PEP-484, should work in all type checkers, so this would appear to be a bug in PyCharm. If you can show me other type checkers that also flag this as an error, I'd be more prone to work around this.