Generic class with typevar inheriting from other class does not resolve super().__init__() call for go to definition

[OlavMSG]

Summary

In VS code when using the F12 go to definition feature.

Example:

class Base:
    def __init__(self, x: int) -> None:
        self.x = x
        print("Base init")


class Generic[T](Base):
    def __init__(self, x: int, y: T):
        # Definition does not resolve to Base.__init__ but super.__init__ using ty,
        # Pylance resolves to Base.__init__
        super().__init__(x) 
        self.y = y
        print("Generic init")

if __name__ == "__main__":

    a = Generic[float](1, 2.3)
    # prints
    # Base init
    # Generic init
    # x=1, y=2.3
    print(f"x={a.x}, y={a.y}")

The super().__init__() call resolves to super.__init__ when using ty.
Switching to Pylance resolves the problem and it resolves to Base.__init__.

It may be wort noting that hovering over the super().__init__(x) displays a "Version

ty 0.0.17

[rafikdraoui]

I'm not sure if this is the same issue, but I get something similar in Neovim even when generic types aren't involved. For example:

from html.parser import HTMLParser


class MyParser(HTMLParser):
    def __init__(self) -> None:
        super().__init__()

Playground link: https://play.ty.dev/dbec440f-12db-4af0-ac44-f9cfbc383045

Doing "Go to Definition" on the __init__ of super().__init__(), two results are returned:

1. The __init__ of the "super" stub in the vendored typeshed's stdlib/builtins.pyi
2. The __init__ of HTMLParser in my Python install's /lib/python3.14/html/parser.py

The second one is the most useful, and this is where it jumps when doing "Go to Definition" in the ty playground. But in Neovim, it jumps to the empty "super stub", presumably because this is the first result that is returned.

(ty version: 0.0.20)