You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Python version (& distribution if applicable, e.g. Anaconda): 2.7.15
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): virtualenv
Relevant/affected Python packages and their versions: None
Expected behaviour
Visual Studio Code navigate to the definition of the function which resides inside the workspace (Working fine earlier)
Actual behaviour
Popup with Message: "No definition found for 'function_name' "
Steps to reproduce:
import the class from another python file
declare and initialize the class
implement any method of the class
after that right click on method and choose go to definition
For example: from commonlib.helpers.general_helper import Helper helper = Helper() user_data = helper.get_user_profile(user_id)
Logs
No logs or errors in console
Things to note
But if you hover the implementation then it will show you the class with function name and all the parameters of the functions that are requested in definition of the function. It's also suggesting the function while implementing. So maybe there is some issue with only "Go to Definition".
Also one more thing if you've written function in same class and use self.method_name() then it will able to navigate to the method
Things I've tried
Tried to reinstall the python extension (ms-python.python) >> Not worked
Tried to install earlier versions of the python extension (ms-python.python) >> Not worked
Closing all the files and reopening of the workspace >> Not worked
Opening the definition file in new tab and tried "Go to definition" >> Not worked
Tried to downgrade VS Code to earlier versions 1.32 and 1.31 >> Not worked
Tried to disable all other extensions except python (ms-python.python) >> Not worked
Please if possible provide an urgent upstream-fix or any temporary fix to resolve this issue.
Don Jayamanne (@DonJayamanne)Eric Snow (@ericsnowcurrently) As per your instruction I've updated the extension to the latest version (2019.4.11987) but the issue is still there and not resolved. I'm still getting popup with message No definition found for 'function_name'
VS Code version: 1.33.1 (Stable Channel) Extension Version (ms-python.python): 2019.4.11987
OS and version: Ubuntu 18.04
Python version (& distribution if applicable, e.g. Anaconda): 2.7.15
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): virtualenv
The problems are:
When goto definition from a class, first goes to the import and then if you click again goes to the real class definition.
But that only happens sometimes, its not reliable, sometimes I have to delete the tags file in vscode so it reindex.
Before the problem started if you click on the method bellow it directed you to the method definition of the class Helllo:
hello = Hello()
hello.method('something')
Now it doesnt work any more.
If anything else i can help you with, please make me know.
Sorry for my previous terrible feedback, its a frustration message.
Absolutely no problem, I can understand how this would impact your work.
Apologies for the inconvenience caused. I can assure you, we have a whole team working just on the language server (the component that provides intellisense, go to definition, etc). However sometimes it can take a while to get fixes out as the causes might not be immediately evident.
Thanks for being patient.
Please note, we've moved the issue to another repo where a separate team can help resolve those issues.
* Close and Open VS Code
* Open a python file
* Open the `Python` output panel or select the command `Python: Show Output`
* Please let me know whether you see `Starting Microsoft Python language server.` in the output (towards the very top).
I have this issue as well, sort of, Go to Definition works for installed packages but not for my local files/workspace.
Follwing the above steps my output is:
Starting Jedi Python language engine.
##########Linting Output - flake8##########
Activity
xavieralt commentedon Apr 24, 2019
Hi,
Just got the same issue after automatic upgrade to new release 2019.4.11881, downgrading extension to 2019.3.6558 solve the issue.
xavieralt commentedon Apr 24, 2019
Seems to be fixed by #5437, manually applying it solve the issue with latest release.
DonJayamanne commentedon Apr 24, 2019
This has been resolved in the latest update, please update your extension.
Duplicate of #5437
kaushall commentedon Apr 25, 2019
Don Jayamanne (@DonJayamanne) Eric Snow (@ericsnowcurrently) As per your instruction I've updated the extension to the latest version (2019.4.11987) but the issue is still there and not resolved. I'm still getting popup with message
No definition found for 'function_name'VS Code version: 1.33.1 (Stable Channel)
Extension Version (ms-python.python): 2019.4.11987
OS and version: Ubuntu 18.04
Python version (& distribution if applicable, e.g. Anaconda): 2.7.15
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): virtualenv
MatthewRuston commentedon Apr 25, 2019
I can also reproduce this using a base case as outlined in the attached screenshot. "Go to Definition" on the
get_name()method no longer works.VS Code:1.33.1
Python Extension:2019.4.11987
Visual Studio IntelliCode - Preview: 1.1.5
OS: mac OS 10.14.2
virtual environment: conda
kaushall commentedon Apr 29, 2019
Don Jayamanne (@DonJayamanne) Eric Snow (@ericsnowcurrently) Any update or ETA for this issue?
monobot commentedon May 7, 2019
Its been working terrible from last update, way worse than sublime.
looking forward for an update, thanks for your work!
MatthewRuston commentedon May 10, 2019
Any update on this? Would additional code samples and test cases help get this fixed?
DonJayamanne commentedon May 10, 2019
Matthew Ruston - WellSky (@MatthewRuston) Héctor Alvarez (@monobot) Kaushal Vora (@kaushall)
Hi everyone, are you using the language server?
Pythonoutput panel or select the commandPython: Show OutputStarting Microsoft Python language server.in the output (towards the very top).DonJayamanne commentedon May 10, 2019
Héctor Alvarez (@monobot)
Please could you provide more information. What's worse, what are the errors.
We need more information to be able to help you.
MatthewRuston commentedon May 10, 2019
Don Jayamanne (@DonJayamanne) definitely running the Python Language Server
monobot commentedon May 10, 2019
Hello Don.
Sorry for my previous terrible feedback, its a frustration message.
Please find your request bellow:
The problems are:
When goto definition from a class, first goes to the import and then if you click again goes to the real class definition.
But that only happens sometimes, its not reliable, sometimes I have to delete the tags file in vscode so it reindex.
Before the problem started if you click on the method bellow it directed you to the method definition of the class Helllo:
Now it doesnt work any more.
If anything else i can help you with, please make me know.
Thanks again for your work.
DonJayamanne commentedon May 10, 2019
Issue moved to microsoft/python-language-server #1064 via ZenHub
DonJayamanne commentedon May 10, 2019
Héctor Alvarez (@monobot)
Absolutely no problem, I can understand how this would impact your work.
Apologies for the inconvenience caused. I can assure you, we have a whole team working just on the language server (the component that provides intellisense, go to definition, etc). However sometimes it can take a while to get fixes out as the causes might not be immediately evident.
Thanks for being patient.
Please note, we've moved the issue to another repo where a separate team can help resolve those issues.
BeyondEvil commentedon May 28, 2019
I have this issue as well, sort of,
Go to Definitionworks for installed packages but not for my local files/workspace.Follwing the above steps my output is:
macOS 10.14.4
VSS 1.34.0
Python 2019.4.12954
python 3.7.3
kaushall commentedon May 28, 2019
Jim Brännlund (@BeyondEvil) This issue has been resolved already.
I think jedi should be disabled.
try to add following line in settings.json >> restart the vscode >> open python file >> check again,
"python.jediEnabled": false,