Go to definition always to module source insted of stub

[luisiacc]

I recommend to, whenever exists a module that have stubs (*.pyi), when triggering Go to Definition, don't ask me if I want to go to the stub file, just go straight to module source file. This feature was implemented in latest python extension of vscode, there, in order to go the the stub file you would have to trigger Go to Implementation, it's not a bad solution. Great extension btw! 👍

[yaegassy]

This behavior has been changed in pyright v1.1.110.

Behavior Change (from Pylance): Separated behavior of "go to definition" and "got to declaration". The former tries to take you to the source, whereas the latter takes you to the stub file.

I think that the expected behavior will be achieved by upgrading the version of pyright used in coc-pyright.

Related:

• https://github.com/microsoft/pyright/releases/tag/1.1.110
• Goto definition goes to stub files instead of actual definitions microsoft/pylance-release#65 (comment)

[fannheyward]

You can :CocUninstall coc-pyright and :CocInstall coc-pyright to upgrade Pyright to latest release. I'll publish a new release of coc-pyright later, with some other fixes.

[AntoineD]

With last coc-pyright and pyright 1.1.115, the behavior has not changed for me and it still goes to the stub file instead of the source code.
Am I missing something to get it right?

[lainisourgod]

@fannheyward I'm not able to go to source files either.

For example, with pandas. When I don't use type stubs, and do GoToDefinition on DataFrame().sample(), I can go to source file.

However, when I use type stubs (from data-science-types) I can only go to type stubs definitions.

[fannheyward]

@meandmymind what's your Pyright version? Checkout :CocCommand pyright.version

[lainisourgod]

@fannheyward coc-pyright 1.1.159 with Pyright 1.1.159