Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Code suggestions not working with Jedi since extension version 2020.5

See original GitHub issue

Environment data

VS Code version: 1.46
Extension version (available under the Extensions sidebar): 2020.6.88468
OS and version: Windows 10
Python version: Python 3.7, Anaconda
Type of virtual environment used: conda
Jedi or Language Server?: Jedi
Value of the python.languageServer setting: Jedi

Behaviour

Code suggestions were working fine with Jedi till version 2020.4.76186. But they stopped working after version 2020.5. I waited for the next release, 2020.6, but they are still not working.

Logs

console.ts:137 [Extension Host] Error Python Extension: 2020-06-17 18:05:24: stderr jediProxy Error (stderr) Traceback (most recent call last): File “xxxxxxxx\.vscode\extensions\ms-python.python-2020.6.88468\pythonFiles\completion.py”, line 661, in watch response = self._process_request(rq) File “xxxxxxxx\.vscode\extensions\ms-python.python-2020.6.88468\pythonFiles\completion.py”, line 599, in _process_request project=jedi.get_default_project(os.path.dirname(path)), AttributeError: module ‘jedi’ has no attribute ‘get_default_project’

Issue Analytics

State:
Created 3 years ago
Comments:6

Top GitHub Comments

2reactions

matthewlloydcommented, Aug 16, 2020

I ran into this issue also. It turns out I had v0.15 installed in my WSL Ubuntu distribution. I ran

sudo pip3 install --upgrade jedi

to fix it. The bug was quite difficult to track down, because searches for information on how to debug the Python extension were not very fruitful. Eventually I discovered it was easy to see the extension output using View -> Output, then select “Python” from the dropdown. I then was able to see the exception, but there was otherwise no visual indication in VSCode that anything had gone wrong. Instead, IntelliSense just hung indefinitely with a “Loading…” message. It would be great to have proper error reporting for this, and for the extension to check the installed version of Jedi during the installation process.

0reactions

kimadelinecommented, Feb 3, 2021

Please open a separate feature request so that we can track this properly.

Thanks!

Top Results From Across the Web

IntelliSense in Visual Studio Code

This can be caused by a variety of reasons. First, try restarting VS Code. If the problem persists, consult the language extension's documentation....

Visual Studio Code: Intellisense not working - Stack Overflow

Solution: Configure the path to the python executable in settings.json . Remember to restart vscode after. The module is located in a non- ......

vscode data viewer not working

Work with Jupyter code cells. .ipynb variable explorer data viewer ... Relevant/affected Python-related VS Code extensions and their versions: Python Test ...

Jedi.el - Python auto-completion for Emacs - (to be determined)

So, running this command after updating Jedi.el each time is recommended. You can configure the location of the Python packages installed by jedi:install-server ......

Jedi - Python autocompletion - Package Control

By default completion for SublimeREPL turned off. If you want use autocompletion feature of SublimeJEDI in a repl, please set enable_in_sublime_repl: true in ......