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
Extension version (available under the Extensions sidebar): 2018.9.0
OS and version: Win 7 x64
Python version (& distribution if applicable, e.g. Anaconda): 3.6, Miniconda
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv
Relevant/affected Python packages and their versions:
Actual behavior
Intellisense is very slow, waiting like 30s for autocompletion on class method, etc., when virtualenv (python -m venv ve) is created in workspace folder.
You should be able to exclude files using the "files.exclude" setting. Otherwise please try the new language server by setting "python.jediEnabled": false.
We're also working to upgrade Jedi in #2667 which may help in this situation.
brettcannon
changed the title
Intellisense (Jedi?) is very slow when virtualenv folder is present in workspace folder on Windows
Intellisense under Jedi is very slow when virtualenv folder is present in workspace folder on Windows
Nov 1, 2018
Did you open the virtual environment as your workspace folder? Basically the entire team works with having a virtual environment locally in the workspace folder and we have not noticed a specific slow-down or performance issue.
Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on then we will be happy to re-open this issue to pick up where we left off.
Environment data
Actual behavior
Intellisense is very slow, waiting like 30s for autocompletion on class method, etc., when virtualenv (python -m venv ve) is created in workspace folder.
The symptomps are very similar to #1810
Expected behavior
Intellisense works with reasonable response time.
Note: I have verified that when I create virtualenv outside the workspace folder and set
python.pythonPath
accordingly, it is reasonably fast.Steps to reproduce:
Ensure Jedi is enabled in User Settings.
Create virtualenv in the workspace folder.
python -m venv ve
Set virtualenv's Python in
python.pythonPath
.Try to get autocompletion on anything, like dictionary method, in a small script (270 LOC in my case).
Note
A nice workaround / solution would be some setting for Jedi to skip selected folders for intellisense
/ autocomplete analysis.
The text was updated successfully, but these errors were encountered: