Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Navigate to source code rather than typeshed #742

Closed
JeroenBos opened this issue Dec 16, 2020 · 1 comment
Closed

Navigate to source code rather than typeshed #742

JeroenBos opened this issue Dec 16, 2020 · 1 comment
Labels
duplicate This issue or pull request already exists

Comments

@JeroenBos
Copy link

I'm looking for a way to navigate to source code of a third-party library. In my experience over the past months sometimes the command "Goto definition" navigates to the actual source code and sometimes to a .pyi file from the pylance typeshed, for the same function.
I have not been able to figure out what affects this.

Given that I prefer the actual source code over the typeshed, is there a setting such that this preference is adhered to, specifically for navigation?

And more generally I'm interested in what settings and state are involved in determining to which to navigate.

There are of course workaround. What I tend to do is to trigger code in the file that I want to use to and let the debugger navigate to that file (the debugger can consistently find the file, so no problem there).
Alternatively I could look up the file manually, but that's often more time consuming. Both feel rather like workarounds.

@jakebailey
Copy link
Member

Duplicate of #65.

@jakebailey jakebailey added the duplicate This issue or pull request already exists label Dec 16, 2020
@github-actions github-actions bot removed the triage label Dec 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants