Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Intellisense under Jedi is very slow when virtualenv folder is present in workspace folder on Windows #3074

Closed
mrkafk opened this issue Oct 31, 2018 · 3 comments
Assignees
Labels
info-needed Issue requires more information from poster

Comments

@mrkafk
Copy link

mrkafk commented Oct 31, 2018

Environment data

  • VS Code version: 1.28.2
  • 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.

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:

  1. Ensure Jedi is enabled in User Settings.

  2. Create virtualenv in the workspace folder.

python -m venv ve

  1. Set virtualenv's Python in python.pythonPath.

  2. 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.

@brettcannon brettcannon self-assigned this Oct 31, 2018
@brettcannon
Copy link
Member

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 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
@brettcannon
Copy link
Member

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.

@brettcannon brettcannon added the info-needed Issue requires more information from poster label Nov 1, 2018
@brettcannon
Copy link
Member

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.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

2 participants