KotlinIsland

Why not both? I imagine the current would be easier for runtime introspection, an aspect that I can only assume mypy overlooked

UYou.pyright+

Edge case: ```py class A: def __new__(cls) -> int: return 1 a = A() ``` I would expect an inlay here, due to the constructor not being typical

Could you please add your full system+python details and installation output. Basedpyright should not require cmake

@DetachHead how do we want to handle this issue? we can't do anything about nodejs-wheel here. do we want to close this issue and open "publish a nodeless release which...

Does the basedpyright plugin for vscode work here?

Invariance?

There is also the scenario of banning non-pep behaviour for public API/evaluated extressions

additionally, generic constraints are now provided with a tuple: ```py def f[T: (int, str)](t: T): ... ```

with the ones in generics, just don't allow it for now, until a more comprehensive solution can be built. for constraints, just take it as a constraint.