Skip to content
This repository was archived by the owner on Apr 14, 2022. It is now read-only.

Python Language Server uses too much CPU #479

Closed
brettcannon opened this issue Dec 11, 2018 · 29 comments
Closed

Python Language Server uses too much CPU #479

brettcannon opened this issue Dec 11, 2018 · 29 comments
Assignees
Labels
bug Something isn't working

Comments

@brettcannon
Copy link
Member

@VelizarVESSELINOV commented on Tue Dec 04 2018

Environment data

  • VS Code version: 1.29.1
  • Extension version (available under the Extensions sidebar): 2018.11.0
  • OS and version: macOS Mojave 10.14.1
  • Python version (& distribution if applicable, e.g. Anaconda): Python 3, Python 2...
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
  • Relevant/affected Python packages and their versions: N/A

Expected behaviour

< 1% CPU

Actual behaviour

> 99% CPU

image

image

image

image

image

Steps to reproduce:

  1. Install several versions of Python
  2. Run VS Code

Logs

Output for Python in the Output panel (ViewOutput, change the drop-down the upper-right of the Output panel to Python)

Starting Microsoft Python language server.
Microsoft Python Language Server version 0.1.65.0
Initializing for /usr/local/bin/python3

@brettcannon commented on Wed Dec 05 2018

Do you have "python.autoComplete.extraPaths" defined?


@PushUpek commented on Thu Dec 06 2018

I have the same issue, but only with python2


@VelizarVESSELINOV commented on Thu Dec 06 2018

@brettcannon only in the default user settings defined as []


@VelizarVESSELINOV commented on Thu Dec 06 2018

It is the biggest CPU consumer of all the processes: >21 hours

image

Side comment that maybe it is the case of @PushUpek I have a lot of files and folders in my current folder that is not Python code or libraries, questioning if Microsoft Python Server is not trying to parse GiB of data continuously in the current folder of VS Code project.


@jonaswitt commented on Mon Dec 10 2018

+1 - I have the same problem with

VS Code 1.29.1
Microsoft Python Language Server version 0.1.65.0
Python Extension 2018.11.0
Python 2.7.15 (venv-based environment)

My python.autoComplete.extraPaths setting is also []. I tried to disable Jedi and Linting. I keep killing the process to keep my Macbook's fans from spinning, but it always respawns at 100% CPU usage.

Is there any way to disable the language server? I believe my only option right now is to disable the python extension completely.


@dwt commented on Mon Dec 10 2018

This happens for me too. Python 2.7 with a moderately big project. What Info can I provide to help debug this?

@munael
Copy link

munael commented Dec 13, 2018

On #3653 (duplicate)

Just in case the differences matter:

I'll have to check on CPU use, but I didn't notice it. I'd guess it's usually reasonable, even when memory use 10GB or higher (most of the time).

I'm on Python 3 not 2, and have only that version of Python installed.

@PushUpek
Copy link

I have couple projects. On python3 is ok. But on python2 cpu usage skips to 100%.

Language Server: 0.1.65

Python output, Extension Output, etc. Is empty, no error messages

@MikhailArkhipov
Copy link

Most probably similar to #495

@MikhailArkhipov MikhailArkhipov added the bug Something isn't working label Dec 19, 2018
@qubitron qubitron added the GA label Dec 20, 2018
@Spongman
Copy link

i can repro this:

  • vscode 1.30.0
  • ms-ms-python.python 4.5 (only extension enabled)
  • git https://github.com/mcedit/mcedit2.git --depth 1
  • hit f12 on a symbol

@max-sixty
Copy link

FWIW I have the same behavior on python3.7 on the xarray repo

I've tried both the current release and the daily channel (Microsoft Python Language Server version 0.1.73.0), and I 100% CPU on both

@drorata
Copy link

drorata commented Jan 10, 2019

Seems like I'm running into the same issue with scikit-learn. 100% and minimal RAM.

@MikhailArkhipov
Copy link

To all folks: we made some tactical fixes, but there is inherent issue to the analysis engine approach.

We are currently working on major restructuring of the static analysis engine that should address the issue with both CPU and memory. If you install Zenhub extension to Chrome, you should be able to track epic #425. The work is not trivial and is not a bug fix level change.

WIP PR #465.

Thanks you for using the LS, the feedback is much appreciated.

@yajo
Copy link

yajo commented Jan 29, 2019

Just as a simple not-so-workaround, how about assigning a lower priority to the spawned process?

On Linux all processes have a value called nice which indicates its priority. A "normal" user process usually uses nice=0. System important processes use lower nice, such as -20; you need to be root to lower the nice. Background, not-so-important processes are expected to use a higher value, such as nice=5.

By doing this very simple patch, we don't fix the CPU leak, but at least we tell the CPU to not block more important processes just for the sake of keep running the language server. Basically, the users wouldn't notice so much this leak. And in any case, it's a good practice for background processes.

I usually renice the LS process and at least it doesn't disturb so much.

I bet other OS have a similar system.

@jakebailey
Copy link
Member

That might be possible. Given this is in C#, we can do:

Process.GetCurrentProcess().PriorityClass = ProcessPriorityClass.BelowNormal;

Which has the effect of setting the nice to 10 on Unix-y platforms.

@jakebailey
Copy link
Member

On second thought, it seems like that'd only help in cases where the system is already using all of its cores at once. If the system has a free core to schedule the process on, it's going to do that even if the nice value is high. I'm not sure that would affect other processes if there are already free cycles...

@Spongman
Copy link

  1. it can't hurt
  2. cache-locality matters
  3. "using all of its cores" happens more often than you might think on a real machine.

@j9ac9k
Copy link

j9ac9k commented Feb 1, 2019

Not sure if you're able to reproduce this issue still or not, I'm happy to provide some log/debug info

OS: macOS 10.14.2
VSCode: 1.30.2
MS-Python Extension: 2019.1.0
Python Version 3.7.2 (via pipenv)

The virutalenv has a large number of dependencies (pyside2, numpy, scipy, pandas..); the codebase isn't particularly large. Python is the only extension currently installed (debug step was to remove VSCode entirely and try again).

Below is everything I could think of as being relevant, but if there is something else that would be helpful, let me know.

User Settings

{
    "python.jediEnabled": false,
    "python.analysis.logLevel": "Trace",
    "python.formatting.provider": "black"
}

workplace settings:

{
    "python.linting.flake8Enabled": true,
    "python.linting.flake8Path": ".venv/bin/flake8",
    "python.linting.flake8Args": ["--config=setup.cfg"],
    "python.linting.pylintEnabled": false,
    "python.unitTest.pyTestEnabled": true,
    "python.unitTest.pyTestPath": ".venv/bin/pytest",
    "python.formatting.blackPath": ".venv/bin/black",
    "python.pythonPath": ".venv/bin/python",
    "python.sortImports.path": ".venv/bin/isort",
    "python.sortImports.args": ["--settings-path ./pyproject.toml"]
}

View -> Output -> Python

Starting Microsoft Python language server.
Downloading https://pvsc.azureedge.net/python-language-server-stable/Python-Language-Server-osx-x64.0.1.78.nupkg... complete
Unpacking archive... done
Microsoft Python Language Server version 0.1.78.0
Initializing for /Users/ognyan/Developer/fred/.venv/bin/python
##########Linting Output - flake8##########
##########Linting Output - flake8##########
Log (Extension host)

[2019-02-01 08:25:33.511] [exthost] [info] extension host started
[2019-02-01 08:25:33.522] [exthost] [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch {"startup":true,"activationEvent":"*"}
[2019-02-01 08:25:33.522] [exthost] [info] ExtensionService#loadCommonJSModule /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/debug-auto-launch/dist/extension
[2019-02-01 08:25:33.524] [exthost] [info] ExtensionService#_doActivateExtension vscode.emmet {"startup":true,"activationEvent":"*"}
[2019-02-01 08:25:33.524] [exthost] [info] ExtensionService#loadCommonJSModule /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/emmet/dist/extension
[2019-02-01 08:25:33.528] [exthost] [info] ExtensionService#_doActivateExtension vscode.git {"startup":true,"activationEvent":"*"}
[2019-02-01 08:25:33.528] [exthost] [info] ExtensionService#loadCommonJSModule /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/git/dist/main
[2019-02-01 08:25:33.549] [exthost] [info] ExtensionService#_doActivateExtension vscode.merge-conflict {"startup":true,"activationEvent":"*"}
[2019-02-01 08:25:33.549] [exthost] [info] ExtensionService#loadCommonJSModule /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/merge-conflict/dist/extension
[2019-02-01 08:25:33.551] [exthost] [info] eager extensions activated
[2019-02-01 08:25:44.582] [exthost] [info] ExtensionService#_doActivateExtension vscode.configuration-editing {"startup":false,"activationEvent":"onLanguage:jsonc"}
[2019-02-01 08:25:44.582] [exthost] [info] ExtensionService#loadCommonJSModule /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/configuration-editing/dist/extension
[2019-02-01 08:25:44.590] [exthost] [info] ExtensionService#_doActivateExtension vscode.json-language-features {"startup":false,"activationEvent":"onLanguage:jsonc"}
[2019-02-01 08:25:44.590] [exthost] [info] ExtensionService#loadCommonJSModule /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/json-language-features/client/dist/jsonMain
[2019-02-01 08:25:44.646] [exthost] [info] ExtensionService#_doActivateExtension vscode.typescript-language-features {"startup":false,"activationEvent":"onLanguage:jsonc"}
[2019-02-01 08:25:44.646] [exthost] [info] ExtensionService#loadCommonJSModule /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension
[2019-02-01 08:26:57.140] [exthost] [info] ExtensionService#_doActivateExtension vscode.python {"startup":false,"activationEvent":"onLanguage:python"}
[2019-02-01 08:26:57.140] [exthost] [info] ExtensionService#loadCommonJSModule /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/python/out/pythonMain
[2019-02-01 08:26:57.142] [exthost] [info] ExtensionService#_doActivateExtension ms-python.python {"startup":false,"activationEvent":"onLanguage:python"}
[2019-02-01 08:26:57.142] [exthost] [info] ExtensionService#loadCommonJSModule /Users/ognyan/.vscode/extensions/ms-python.python-2019.1.0/out/client/extension
[2019-02-01 08:27:12.143] [exthost] [error] [ms-python.python] provider FAILED
[2019-02-01 08:27:12.143] [exthost] [error] TypeError: Cannot read property 'map' of undefined
	at asCompletionResult (/Users/ognyan/.vscode/extensions/ms-python.python-2019.1.0/out/client/extension.js:83:96546)
	at <anonymous>
[2019-02-01 08:27:27.567] [exthost] [error] [ms-python.python] provider FAILED
[2019-02-01 08:27:27.567] [exthost] [error] TypeError: Cannot read property 'map' of undefined
	at asCompletionResult (/Users/ognyan/.vscode/extensions/ms-python.python-2019.1.0/out/client/extension.js:83:96546)
	at <anonymous>
[2019-02-01 08:27:28.768] [exthost] [error] [ms-python.python] provider FAILED
[2019-02-01 08:27:28.768] [exthost] [error] TypeError: Cannot read property 'map' of undefined
	at asCompletionResult (/Users/ognyan/.vscode/extensions/ms-python.python-2019.1.0/out/client/extension.js:83:96546)
	at <anonymous>}}

Log (Window)

[2019-02-01 08:25:33.472] [renderer3] [info] no standard startup: not just one window
[2019-02-01 08:27:12.144] [renderer3] [error] Cannot read property 'map' of undefined: TypeError: Cannot read property 'map' of undefined
	at asCompletionResult (/Users/ognyan/.vscode/extensions/ms-python.python-2019.1.0/out/client/extension.js:83:96546)
	at <anonymous>
[2019-02-01 08:27:27.568] [renderer3] [error] Cannot read property 'map' of undefined: TypeError: Cannot read property 'map' of undefined
	at asCompletionResult (/Users/ognyan/.vscode/extensions/ms-python.python-2019.1.0/out/client/extension.js:83:96546)
	at <anonymous>
[2019-02-01 08:27:28.769] [renderer3] [error] Cannot read property 'map' of undefined: TypeError: Cannot read property 'map' of undefined
	at asCompletionResult (/Users/ognyan/.vscode/extensions/ms-python.python-2019.1.0/out/client/extension.js:83:96546)
	at <anonymous>

Log (Shared)

[2019-02-01 08:25:06.261] [sharedprocess] [info] main {"machineId":"78630bf7d35a0ab3bd8c5a2362a1bcc05eac83d48c7423f7ea566f5fce023116"}
[2019-02-01 08:25:06.287] [sharedprocess] [info] Scanned user extensions: 0
[2019-02-01 08:25:06.311] [sharedprocess] [info] Scanned user extensions: 0
[2019-02-01 08:25:06.319] [sharedprocess] [info] Scanned user extensions: 0
[2019-02-01 08:25:06.328] [sharedprocess] [info] Scanned user extensions: 0
[2019-02-01 08:25:06.380] [sharedprocess] [info] Scanned system extensions: 71
[2019-02-01 08:25:06.388] [sharedprocess] [info] Scanned system extensions: 71
[2019-02-01 08:25:06.390] [sharedprocess] [info] Scanned system extensions: 71
[2019-02-01 08:25:14.994] [sharedprocess] [info] Scanned user extensions: 0
[2019-02-01 08:25:14.999] [sharedprocess] [info] Scanned user extensions: 0
[2019-02-01 08:25:15.000] [sharedprocess] [info] Scanned user extensions: 0
[2019-02-01 08:25:15.010] [sharedprocess] [info] Scanned user extensions: 0
[2019-02-01 08:25:15.072] [sharedprocess] [info] Scanned system extensions: 71
[2019-02-01 08:25:15.074] [sharedprocess] [info] Scanned system extensions: 71
[2019-02-01 08:25:15.077] [sharedprocess] [info] Scanned system extensions: 71
[2019-02-01 08:25:19.176] [sharedprocess] [info] Installing extension: python
[2019-02-01 08:25:19.178] [sharedprocess] [info] Scanned user extensions: 0
[2019-02-01 08:25:19.771] [sharedprocess] [info] Downloaded extension: python /var/folders/49/mw4m6yx97t3dv9y_pjvdbm400000gn/T/27bacb49-061c-4630-90a8-8c9eb5d05f86
[2019-02-01 08:25:20.754] [sharedprocess] [info] Extracted extension to /Users/ognyan/.vscode/extensions/.ms-python.python-2019.1.0: ms-python.python-2019.1.0
[2019-02-01 08:25:20.755] [sharedprocess] [info] Renamed to /Users/ognyan/.vscode/extensions/ms-python.python-2019.1.0
[2019-02-01 08:25:20.758] [sharedprocess] [info] Installation completed. ms-python.python-2019.1.0
[2019-02-01 08:25:20.793] [sharedprocess] [info] Extensions installed successfully: ms-python.python
[2019-02-01 08:25:20.905] [sharedprocess] [info] Scanned user extensions: 1
[2019-02-01 08:25:20.907] [sharedprocess] [info] Scanned user extensions: 1
[2019-02-01 08:25:20.937] [sharedprocess] [info] Scanned system extensions: 71
[2019-02-01 08:25:20.939] [sharedprocess] [info] Scanned system extensions: 71
[2019-02-01 08:25:22.651] [sharedprocess] [info] Scanned user extensions: 1
[2019-02-01 08:25:22.652] [sharedprocess] [info] Scanned user extensions: 1
[2019-02-01 08:25:22.654] [sharedprocess] [info] Scanned user extensions: 1
[2019-02-01 08:25:22.666] [sharedprocess] [info] Scanned user extensions: 1
[2019-02-01 08:25:22.668] [sharedprocess] [info] Scanned user extensions: 1
[2019-02-01 08:25:22.729] [sharedprocess] [info] Scanned system extensions: 71
[2019-02-01 08:25:22.731] [sharedprocess] [info] Scanned system extensions: 71
[2019-02-01 08:25:22.733] [sharedprocess] [info] Scanned system extensions: 71
[2019-02-01 08:25:22.735] [sharedprocess] [info] Scanned system extensions: 71
[2019-02-01 08:25:22.744] [sharedprocess] [info] Scanned user extensions: 1
[2019-02-01 08:25:33.225] [sharedprocess] [info] Scanned user extensions: 1
[2019-02-01 08:25:33.227] [sharedprocess] [info] Scanned user extensions: 1
[2019-02-01 08:25:33.282] [sharedprocess] [info] Scanned system extensions: 71
[2019-02-01 08:25:33.285] [sharedprocess] [info] Scanned system extensions: 71
[2019-02-01 08:25:33.504] [sharedprocess] [info] Scanned user extensions: 1
[2019-02-01 08:25:36.611] [sharedprocess] [info] Scanned user extensions: 1
[2019-02-01 08:25:46.265] [sharedprocess] [info] Starting to clean up unused language packs.
[2019-02-01 08:26:57.143] [sharedprocess] [info] Scanned user extensions: 1
[2019-02-01 08:26:57.163] [sharedprocess] [info] Scanned system extensions: 71
[2019-02-01 08:30:33.510] [sharedprocess] [info] Scanned user extensions: 1
[2019-02-01 08:35:33.505] [sharedprocess] [info] Scanned user extensions: 1
[2019-02-01 08:40:33.503] [sharedprocess] [info] Scanned user extensions: 1
[2019-02-01 08:45:33.498] [sharedprocess] [info] Scanned user extensions: 1
[2019-02-01 08:50:33.496] [sharedprocess] [info] Scanned user extensions: 1
[2019-02-01 08:55:33.491] [sharedprocess] [info] Scanned user extensions: 1
[2019-02-01 09:00:33.489] [sharedprocess] [info] Scanned user extensions: 1
[2019-02-01 09:05:33.482] [sharedprocess] [info] Scanned user extensions: 1
[2019-02-01 09:10:33.480] [sharedprocess] [info] Scanned user extensions: 1
[2019-02-01 09:15:33.475] [sharedprocess] [info] Scanned user extensions: 1
[2019-02-01 09:16:04.085] [sharedprocess] [info] Scanned user extensions: 1
[2019-02-01 09:16:04.088] [sharedprocess] [info] Scanned user extensions: 1
[2019-02-01 09:16:04.090] [sharedprocess] [info] Scanned user extensions: 1
[2019-02-01 09:16:04.099] [sharedprocess] [info] Scanned user extensions: 1
[2019-02-01 09:16:04.160] [sharedprocess] [info] Scanned system extensions: 71
[2019-02-01 09:16:04.162] [sharedprocess] [info] Scanned system extensions: 71
[2019-02-01 09:16:04.164] [sharedprocess] [info] Scanned system extensions: 71
[2019-02-01 09:20:33.469] [sharedprocess] [info] Scanned user extensions: 1
[2019-02-01 09:25:33.502] [sharedprocess] [info] Scanned user extensions: 1

Log (Main)

[2019-02-01 08:25:02.715] [main] [info] update#setState idle
[2019-02-01 08:25:32.719] [main] [info] update#setState checking for updates
[2019-02-01 08:25:32.873] [main] [info] update#setState idle
[2019-02-01 09:25:32.571] [main] [info] update#setState checking for updates
[2019-02-01 09:25:32.700] [main] [info] update#setState idle

EDIT: Let my machine run over the weekend; still running at ~100% CPU

screen shot 2019-02-04 at 9 05 29 am

@luckb0x
Copy link

luckb0x commented Feb 5, 2019

OS: macOS 10.14.2
VSCode: 1.30.2
MS-Python Extension: 2019.1.0
Microsoft Python Language Server version 0.1.78.0

I'm having a similar issue on my MBP, where Microsoft.Python.LanguageServer is running up to 100%+ CPU usage when I have large Python projects open (one, in particular, is ~200MB) within a virtual environment.

I have tested this with both Python 3.6.7 (from the official website), Python 2.7.15 (installed from Brew and another that's native to Mac). All versions in the virtual environment exhibit similar behavior.

I have this python.jediEnabled set to true & false.
Additionally, I have linting disabled, so there's no additional overhead from that POV.

Very frustrating, as my CPU is normal when I use Atom or PyCharm with the same project. Please let me know if I can help in any way to try and get to the bottom of this.

@jakebailey
Copy link
Member

Please see this comment above: #479 (comment)

The story hasn't changed; it's still being worked on. See here for specific issues: https://github.com/Microsoft/python-language-server/issues?q=label%3AGA

(I also responded in the other thread you commented on).

@MikhailArkhipov
Copy link

#546

@j9ac9k
Copy link

j9ac9k commented Feb 6, 2019

Please forgive me for commenting on a closed issue.

Congratulations on that pull request, that looks like a ton of work went into this, thank you. I am curious if you know know what version of the Language Server will incorporate that pull request or when it will go live?

Thanks again for this awesome tool.

@MikhailArkhipov
Copy link

If you install Zenhub extension to Chrome, you should be able to see our schedule. Specifically, the Release report.

https://github.com/Microsoft/python-language-server#workspaces/python-language-server-5b897936af3c0a2186966c0f/reports?report=release&release=5c469ca115d68f55b9388c22

@BilalDendani
Copy link

I am also have the same problem with the following version
Version: 1.32.3
Commit: a3db5be9b5c6ba46bb7555ec5d60178ecc2eaae4
Date: 2019-03-14T23:38:49.842Z
Electron: 3.1.6
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Linux x64 4.18.19-100.fc27.x86_64

@maxn0d3x
Copy link

this sucks !!!

@VelizarVESSELINOV
Copy link

@MikhailArkhipov @brettcannon

It is exceptional to see so badly managing resource piece of software in production with known bugs (and/or bad design) since months and still not fixed. Not sure what it is wrong the management of the project or people working on this project or the testing, but it is very difficult for users of VS Code (Python on Mac...) to trust the capacity of Microsoft to produce good quality software.

What is the required hardware capacity to run VS Code with Python (on Mac)? 70 GiB RAM for VS Code?

image

@jakebailey
Copy link
Member

This is not normal, it is a bug. We have been working for many weeks on performance improvements, including memory usage. At the latest revision, analyzing tensorflow on my machine only uses 400 MB, as opposed to the multiple gigabytes it used to take. If you have a project which reproduces it, we'd love to test it and figure out why that would occur.

Also, try switching up to the beta release, which has many more improvements not yet in stable.

"python.analysis.downloadChannel": "beta"

@jakebailey
Copy link
Member

#832

@VelizarVESSELINOV
Copy link

@jakebailey I understand that this is a bug, I'm happy to see that you are working on fixing it, but the problem of abusive usage of resources is not new. This ticket is more six months old, and there was other as well earlier Q4 last year. I'm surprised that it is taking you more than six months to fix it, plus have the feeling that is going backward not reducing the resources used but increasingly. 20-40 GB was the "normal" level a few months ago, and now it is 70 GB.

I hope that soon you will fix it, and not again add small patches that solve few loading pick issues. The hidden requirement to restart many times per day VS Code reminds me of the old times of Windows.

@esbozos
Copy link

esbozos commented May 12, 2019

Captura de Pantalla 2019-05-12 a la(s) 2 27 46 a  m

Analyzing workspace of Microsoft.Python.LanguageServer at the early start of opening, is a killing resources machines, is just like a python surrounding your neck, iI disabled other extensions, Jedi False, and the server just takes all available resources as a desperately hungry that just return from the jungle ...

Please let me know if you have some tips, tricks or guidance to resolve or how we can help to resolve this.

@esbozos
Copy link

esbozos commented May 12, 2019

Reading related reports issues, and testing, I got an improvement that helps me a few.
Setting the download channel to "beta" version, the log level "Trace" and Jedi False btw.

"python.analysis.logLevel": "Trace",
"python.analysis.downloadChannel": "beta",
"python.jediEnabled": false

@ipstone
Copy link

ipstone commented Jul 9, 2019

Thank you for the work on python language server.

I am a happy user of vscode, but when it comes to python code in my project, I have to switch to sublime etc., because python package is bundled together with language server (I might be wrong), and now I also have this issue of very high cpu usage, (I have relative faster macbook air with i7 processor)...

Is it possible to separate the python extension and python language server?

@jakebailey
Copy link
Member

You can disable the language server by setting python.jediEnabled to true. The language server is not enabled by default in the Python extension; you would have needed to enable it explicitly to have it run.

@chienjchienj
Copy link

Setting python.jediEnabled to true works for me

but it keeps showing this....
image

Is there a way to ignore this permanently?

@jakebailey
Copy link
Member

You can't use Jedi with IntelliCode; IntelliCode's Python support is an extension to the language server. That gear button may offer a way, but past that I do not know other than to remove IntelliCode.

Be aware that we've just built 0.3.22, which is available in the beta/daily channels. It contains some fixes which can help. You can set this and reload to update:

"python.analysis.downloadChannel": "beta"

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests