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
"Python extension loading..." #6687
Comments
Thanks for letting us know about this, @tburd. The information you've provided is useful. We're reviewing the log. In the meantime... Do you see the problem with a minimal workspace (a folder with a single basic .py file, e.g. Also, what do you have in your user settings.json and your workspace settings.json? |
The only thing I find suspicious is the following part of the log:
The rest seems okay. The extension found Anaconda. There isn't any extra work going on. What happens if you switch over to Jedi ( |
Hi Eric, I performed the test you mentioned:
Remarks:
|
@ericsnowcurrently Outcome:
I was quite happy for some moments 😄 settings.json{
"update.channel": "none",
"workbench.welcome.enabled": false,
"workbench.tips.enabled": false,
"telemetry.enableTelemetry": false,
"telemetry.enableCrashReporter": false,
"terminal.integrated.shell.windows": "C:\\WINDOWS\\Sysnative\\WindowsPowerShell\\v1.0\\powershell.exe",
"editor.tabSize": 10,
"window.zoomLevel": 0,
"editor.fontSize": 12,
"editor.mouseWheelZoom": true,
"workbench.colorTheme": "Monokai",
"files.autoSave": "off",
"python.venvPath": "C:\\ProgramData\\Anaconda3\\venvs\\",
"terminal.integrated.fontSize": 12,
"code-runner.saveFileBeforeRun": true,
"git.path": "C:\\Program Files\\Git\\bin\\git.exe",
"git.enabled": true,
"terminal.integrated.rendererType": "dom",
"extensions.autoUpdate": false,
"python.jediEnabled": true
} Current log:
|
So, with a fresh simple workspace you do not see the problem? If that's the case then there certainly may be some complication either due to that older version of VS Code (my guess) or due to the existing workspaces. Could you try with a fresh workspace on a fresh clone of one of the existing workspaces that is causing the problem? Is there a way to uninstall that older VS Code or to completely update it? There may be a problem if they are both trying to use the same data directory. |
Hi @ericsnowcurrently I did the following:
Log from last action
Question:
|
@ericsnowcurrently would you recommend me testing anything else? Should I switch back to an older version of VS Code (user)? Best regards! |
Additional info:
|
Sorry we haven't made any headway on this, @tburd. From what you are saying, everything works fine after installing/upgrading/downgrading the extension and then in some later session the extension stops loading. Is it the very next time or after X sessions or after a X time or just at random? @DonJayamanne, any ideas? As to the per-workspace .vscode directory, it isn't necessary. It is where customizations to your various settings are put. So if the file is missing then it means you are using all the defaults (or user settings). |
Thanks for the support @ericsnowcurrently. |
That's helpful info, @tburd. I'm going to look into what sorts of problems might be related. To be honest, I'm a bit stumped on this. (We're not giving up, though!) In the meantime, there's one thing I want to check. Let's assume that, after an install in the current session, some data related to the extension is loaded straight into memory rather than from disk. If that is the case then it almost sounds like the problem would be with those parts when they are loaded from disk. Is VS Code or the extension installed on a local disk? Is your home directory on that same local disk? |
@ericsnowcurrently, thanks for the answer. VS Code is installed in: C:\User\MYUSER\AppData\Local\Programs\Microsoft VS Code Although all my working folders and files are in a network drive. Regards |
Yeah, that helps. We'll get back to you as soon as we have more info (or questiosn). |
@tburd, thus far I haven't been able to find what might be causing the problem here. Is this something you are still seeing after the latest release of the extension? Also, what is the "j:\ROOT\0. Topics\python_\New folder.vscode" that showed up in the logs you posted in #6687 (comment)? Is your workspace located on a different drive? |
@ericsnowcurrently, recently I updated to Windows 10, installed newest version of VS Code user install and latest extension release. Everybody is working like a charm! |
@tburd, I am so glad to hear that! Sorry we couldn't figure out the problem. I suppose it shouldn't be surprising that it was probably something related to Windows 7 (though I suppose it could have been corrupt data in VS Code or the extension). Regardless, please let us know if you run into any other trouble. |
Environment data
Expected Behavior
The "Python extension loading..." message at the bottom should disappear and the extension should be usable
Actual behavior
The message last forever and the extension isn't usable
Additional info:
I looked several other issues reported from different users and none was able to solve my problem #5599 [Extension does not load, stuck at "Python extension loading..." #6392] [Python extension does not load #4114] [Long loading times for Python extension #2878]
I tried to installed older versions of the VS Code and had same behaviour
When I change versions of the extension, then it works (going back to an older version, and coming back to the most recent one). Although when I close and restart VS Code, the problem is there again.
I already tested several versions, including installation from .VSIX
I also tried to update the Language Server (according to the current pinned topic). And it worked, although after restarting the application had the error again.
Steps to reproduce:
Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)
The text was updated successfully, but these errors were encountered: