Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Support "go to definition" for namespace packages #231

Copy link
Copy link
Closed
@swarnendubiswas

Description

@swarnendubiswas
Issue body actions

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.

Metadata

Metadata

Labels

feature-requestRequest for new features or functionalityRequest for new features or functionality

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    Morty Proxy This is a proxified and sanitized view of the page, visit original site.