Prefer __new__ over __init__ for determining callable type of a class #5647

Activity

1. hauntsaninja commented on Feb 25, 2020

   

   hauntsaninja

   on Feb 25, 2020

   Collaborator

   More actions

   Here's an example (simplified from a post in the gitter today) where we get a terrible error message because IntEnum subclasses int.

   ~/delete λ cat test34.py
   from enum import IntEnum
   
   IntEnum("Fruit", "Apple Pear")
   ~/delete λ mypy test34.py
   test34.py:3: error: No overload variant of "IntEnum" matches argument types "str", "str"
   test34.py:3: note: Possible overload variant:
   test34.py:3: note:     def IntEnum(self, x: Union[str, bytes, bytearray], base: int) -> IntEnum
   test34.py:3: note:     <1 more non-matching overload not shown>
   Found 1 error in 1 file (checked 1 source file)
   

   Curious if you remember what the problematic typeshed __new__s are?
2. hauntsaninja

   added 3 commits that reference this issue on Nov 3, 2024

   Fix __new__ and __init__ precedence

   ...

   This issue will close once commit ce89220 is merged into the 'master' branch.

   ce89220

   Fix __new__ and __init__ precedence

   ...

   This issue will close once commit 5a40f11 is merged into the 'master' branch.

   5a40f11

   Fix __new__ and __init__ precedence

   ...

   This issue will close once commit ee93b0b is merged into the 'master' branch.

   ee93b0b
3. hauntsaninja

   added a commit that references this issue on Dec 27, 2024

   Fix __new__ and __init__ precedence

   ...

   This issue will close once commit 137dd74 is merged into the 'master' branch.

   137dd74