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
{{ message }}
This repository was archived by the owner on Apr 14, 2022. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 14, 2022. It is now read-only.
Following the advice from this thread which was closed prematurely microsoft/vscode-python#2149, I switched to the Microsoft Python language server, but the same explosion in CPU/memory use I noted before disabling both Jedi and Pylint continued unabated using this server. My .py file is about 1200 lines of code, but it's the only one open and being linted/checked. This doesn't even consider what affect attempting to tab-complete or inspect a module might have. .
Christopher Ivan (@ctivanovich) - length of your code is not an issue, it is typically libraries you import that can be very large. Please specify which packages you import, what is the version of the LS (displayed at startup) and how long did you wait.
We close issues as specific case is fixed so if the case is different, new issue is recommended so it can be assigned properly depending on the area that causes the problem.
Activity
MikhailArkhipov commentedon Apr 10, 2019
Christopher Ivan (@ctivanovich) - length of your code is not an issue, it is typically libraries you import that can be very large. Please specify which packages you import, what is the version of the LS (displayed at startup) and how long did you wait.
We close issues as specific case is fixed so if the case is different, new issue is recommended so it can be assigned properly depending on the area that causes the problem.
Thanks
[-]Heavy CPU usage #2149 still an issue, prematurely closed[/-][+]Heavy CPU usage[/+]MikhailArkhipov commentedon May 21, 2019
Christopher Ivan (@ctivanovich) - has it improved since? Thanks
ctivanovich commentedon May 27, 2019
It seems, at least for now, the language server has calmed down, thanks.