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.

Intellisense hangs with `Loading...`

See original GitHub issue

Environment data

VS Code version: 1.19.0 Python Extension version: 0.9.0 Python Version: 3.6.3 OS and version: MacOS 10.13.2

Actual behavior

Intellisense hangs indefintely with Loading... when hovering over a function.

Expected behavior

Intellisense provides documentation about the function.

Steps to reproduce:

Hover over a function

Output from Console window (Help->Developer Tools menu)

Python Extension: error jediProxy, Error (error) Error: spawn python3 ENOENT null

Additional Information

I just updated to 0.9.0 and Intellisense stopped workings.

It seems that the extension cannot find python3 on my path. I installed python3 using homebrew in /usr/local/. I prepend /usr/local/ to my PATH in .profile and .zprofile. I also activate my default python3 virtualenv in my .zshrc.

Running python3 programs works in the vscode integrated terminal. This bug occurs regardless of whether I launch vscode from either the terminal or the application folder. This bug may be related to saravanan-k90/python-jedi#9.

Let me know if there’s any way I can help!

Issue Analytics

State:
Created 6 years ago
Reactions:8
Comments:13 (2 by maintainers)

Top GitHub Comments

3reactions

markobaloghcommented, Dec 15, 2017

Same issue for me. Everything working until I updated…I downgraded my vs code to 1.18.1 to check if it was the VS code update but it still doesn’t work in the previous VS code version—I have no python intellisense functionality, just hangs on “loading…”. VS code version: 1.18.1 Python extension 0.9.0 Python 3.6.0 Mac OS 10.13.2

Update:

For me, the problem was caused by the python.pythonPath variable in my VS code settings. Before, I had simply used python3 and this was ok. Now, after noticing the python debugger asking me to validate the python path, I changed it to a fully qualified path (pasting in the result of running $ which python3 in terminal), and that seems to have fixed both my debugger issues and the intellisense issues mentioned above.

3reactions

Hobinxcommented, Dec 16, 2017

Working fine until I upgraded to vscode 1.19.0, same problem occurred.

Update:

After explicitly set the python.pythonPath to the fully qualified path of my virtual env’s python, the problem seems to be fixed.

Top Results From Across the Web

Intellisense loading forever - visual studio - Stack Overflow

Any similar experience or how it can be fixed? Basically whenever I try to see the methods of a class or refactor something...

How To Fix Visual Studio Code IntelliSense Loading Infinitely

In this short article, I'm sharing the reason of this issue and my way of fixing it. How VS Code Infinite IntelliSense Loading...

VS 2019, 2022 stuck at "loading intellisense"

I any project I open will never finish loading intellisense. UI eventually hangs if I try to close UI, switch from debug/release, or...

Intellisense shows loading indefinitely · Issue #87870 - GitHub

Open a project in visual studio code(React). ... 3.You can find the intellisense working perfectly. 4.Do npm install (add node modules) then try ......

Intellisense stuck at "Loading Constraints" v 15.1

When using Intellisense CTRL+. for something like a table / partial proc name in Toad 15.1.113.1379, it gets stuck on "Loading Constraints", ...