Support "go to definition" for namespace packages

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.

[swarnendubiswas]

@brettcannon This is a quite late follow up to your comment about packages not having a __init__.py. However, Go to definition does not work even if I add a __init__.py.

FYI, I can navigate these definitions in Atom.

[elliott-beach]

FYI The Jedi issue for this is https://github.com/davidhalter/jedi/issues/959. (There is also https://github.com/davidhalter/jedi/issues/122 for explicit namespace packages). It would make more sense to patch Jedi than fix it here, probably.