Support "go to definition" for namespace packages

[swarnendubiswas]

Environment data

VS Code version: 1.18.0
Python Extension version: 0.8.0
Python Version: 3.5.4
OS and version: CentOS 7.4

Actual behavior

1. I have run exuberant ctags and have generated tags file in ${workspaceRoot}/.vscode/tags. I have also set "python.autoComplete.extraPaths": [
   "${workspaceRoot}/src"
   ].
2. Select a function call and press F12, "Go to definition". Visual Studio Code says "No definition found".

Expected behavior

1. I expect Visual Studio Code to jump to the right tag. "Go to symbol in workspace" is able to find the matching tag.

What is confusing for me is that "go to definition" works for a few method calls, but not for all.

Steps to reproduce:

• 1. Select a function call and press F12, "Go to definition". Visual Studio Code says "No definition found".

Logs

Output from Python output panel
No valid output.

Output from Console window (Help->Developer Tools menu)
No valid output.

[DonJayamanne]

@swarnendubiswas Please could you provide a code sample of a scenario where 'Go to definition' does not work.

[swarnendubiswas]

I understand, but I am referring to a multi-module multi-file project I am working on. I will need to try and create a dummy project to reproduce the problem.

Instead for now, I have attached a screenshot.

Refer to the static method calls In the screenshot: RunTask.runBench() (line 16) and StatsTask.extractStats() (line 24). VSC is unable to go to definition. It cannot also jump to definition for calls like options.setInputTupleFromStats() (line 38) where options is a object.

However, VSC can jump to definition for util.computeInputsFromStats() where util is the module.

[DonJayamanne]

I understand, but I am referring to a multi-module multi-file project I am working on

Hmm, thats new information.
Without a proper sample its very difficult to assist. I'll try my best.
When using multi-root workspaces or similar, you'd have problems with paths (we're using Jedi to perform static analysis of the code base to provide intellisense).

Assuming you have the following structure in a multiroot scenario:

• FolderA
• FolderB

When using modules from FolderA from code in FolderB, you'd need to modify your PYTHONPATH to help intellisense. One way of doing this is as follows:

• Create a .env file in your FolderB workspace root
• Add the following PYTHONPATH=../FolderA (this ensures FolderA will be added into your PYTHONPATH for vscode)
• Restart VS Code

[swarnendubiswas]

I have attached a dummy project consisting of a few modules and class definitions. Go to definition does not work for me from the main() function. Please check.
dummy-project.tar.gz