Too many arguments for IntEnum reported

[Spenhouet]

If I define the following IntEnum:

Numbers = IntEnum('Numbers', ['ZERO', 'ONE', 'TWO'], start=0)

mypy throws the following lint error: Too many arguments for IntEnum().

The start parameter is an official methods:

use the start parameter to specify a different starting value

https://docs.python.org/3/library/enum.html

[Michael0x2a]

Yeah, it looks like the checks in https:/python/mypy/blob/master/mypy/semanal_enum.py#L99 are too strict.

If you're feeling up for submitting a PR, I think it would probably be good enough relax the checks so they make sure there are only two positional arguments, not just two arguments in total, and that the keyword arguments all have the right names -- see call.arg_kinds, call.arg_names, and https:/python/mypy/blob/master/mypy/nodes.py#L1501.

And if you also feel like checking the type, we can probably get away with insisting the user always uses an int literal for start. (Supporting arbitrary variables is tricky, since we special-case handling enums before the type checking phase).

Not sure if it's worth trying to support the other keyword arguments though, especially module and qualnames: idk what mypy would do with them.

[rahulrj]

@JukkaL is this a feature or a mypy bug? Can i submit a PR for this?

[mridullpandey]

hi bro @rahulrj are you working on it...

[swetavooda]

If nobody is assigned for this issue, I would like to work on it.

[rahulrj]

I am not working on this @mridullpandey

[mridullpandey]

hi @swetavooda i have did some sort of modifications on it,will you please take another one ..pls let me know asap thanks :-)

[mridullpandey]

@Michael0x2a will you please elaborate it what to actually do

[swetavooda]

@mridullpandey If you are really willing to work on this, you may continue. I'll find another issue to work on.

[Arshaan-256]

Merge pull request #8436. Hopefully that would fix the issue.

[mridullpandey]

then why this is still alive
@Arshaan-256

[Arshaan-256]

@mridullpandey Because it hasn't been reviewed yet. Once the PR is reviewed by the collaborator, only then can the issue be closed. The PR has passed the tests as well.

[killthekitten]

What's the status on this one?

[momohatt]

This seems to have been already fixed in #9123

[JelleZijlstra]

Indeed, closing this issue