René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Support \"go to definition\" for namespace packages","articleBody":"## Environment data\r\nVS Code version:  1.18.0\r\nPython Extension version:  0.8.0\r\nPython Version:   3.5.4\r\nOS and version:   CentOS 7.4\r\n\r\n## Actual behavior\r\n1) I have run exuberant ctags and have generated tags file in ${workspaceRoot}/.vscode/tags. I have also set \"python.autoComplete.extraPaths\": [\r\n        \"${workspaceRoot}/src\"\r\n    ].\r\n2) Select a function call and press F12, \"Go to definition\". Visual Studio Code says \"No definition found\".\r\n\r\n## Expected  behavior\r\n1) I expect Visual Studio Code to jump to the right tag. \"Go to symbol in workspace\" is able to find the matching tag.\r\n\r\nWhat is confusing for me is that \"go to definition\" works for a few method calls, but not for all. \r\n\r\n## Steps to reproduce:  \r\n- 1) Select a function call and press F12, \"Go to definition\". Visual Studio Code says \"No definition found\".\r\n-  \r\n\r\n## Logs\r\nOutput from ```Python``` output panel  \r\nNo valid output.\r\n```\r\n```   \r\nOutput from ```Console window``` (Help-\u003eDeveloper Tools menu)\r\nNo valid output.\r\n```\r\n```\r\n","author":{"url":"https://github.com/swarnendubiswas","@type":"Person","name":"swarnendubiswas"},"datePublished":"2017-11-15T16:20:08.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":19},"url":"https://github.com/231/vscode-python/issues/231"}