Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

"Go to definition" on module takes you to init.py instead of actual module

See original GitHub issue

Environment data

VS Code version: 1.29.1
Extension version (available under the Extensions sidebar): 2018.11.0
OS and version: Windows 10 64-bit
Python version (& distribution if applicable, e.g. Anaconda): Conda 3.7.1
Type of virtual environment used (N/A | venv | virtualenv | conda | …): venv
Relevant/affected Python packages and their versions: None

Actual behavior

“Go to definition” on module takes me to __init__.py rather than the module I actually selected.

Expected behavior

“Go to definition” on module takes me to the module I selected.

Steps to reproduce:

Using the jedi language engine:

gotodef_debug

Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

# there is no output, as seen in the screencap above

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)

# there is no output, as seen in the screencap above

Issue Analytics

State:
Created 5 years ago
Reactions:2
Comments:14 (1 by maintainers)

Top GitHub Comments

2reactions

DonJayamannecommented, Jan 31, 2019

Unable to replicate in the latest version of Jedi and parso, hence we should upgrade.

1reaction

fredrikaverpilcommented, Dec 21, 2019

@brettcannon I cannot reproduce this anymore in vscode 1.41.1. To me, this issue seems completely fixed. I’ve tested the same case as above with both jedi and the python language server! 👍 🎉