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

"Go To Definition" prefers module outside workspace #12051

Closed
zbs opened this issue May 29, 2020 · 3 comments
Closed

"Go To Definition" prefers module outside workspace #12051

zbs opened this issue May 29, 2020 · 3 comments

Comments

@zbs
Copy link

zbs commented May 29, 2020

Environment data

VS Code version: 1.43.2
Extension version (available under the Extensions sidebar): 2020.5.80290
OS and version: Windows 10 Enterprise V 1909
Python version (& distribution if applicable, e.g. Anaconda): python27
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): none

Note that I am connecting to a Linux filesystem from Windows via the Remote-SSH extension. Inside that remote directory, I installed the Python extension.

Actual Behavior

project/
    .vscode/
        settings.json
    foo.py
    bar.py
otherfolder/bar.py

In foo.py:
import bar
When I CTRL+Click on bar, it brings me to otherfolder/bar.py, instead of project/bar.py. It's worth noting that this filesystem has multiple interpreters, and has an extensive PYTHONPATH, but I don't think those affect how the Python intellisense does module lookup.

@ghost ghost added the triage-needed Needs assignment to the proper sub-team label May 29, 2020
@brettcannon
Copy link
Member

Unfortunately you didn't fill out the issue template which asks which language server you are using. Can you please answer that question?

@zbs
Copy link
Author

zbs commented Jun 1, 2020

I'm using the JEDI language server.

FYI, when I use the MS Language Server, CTRL+CLICK hangs indefinitely.

@karthiknadig
Copy link
Member

this should be addressed via #11995

@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Jun 2, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 16, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants