-
Notifications
You must be signed in to change notification settings - Fork 315
WPy64-3940_VSCode not portable #1002
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
Comments
Do you launch vscode via the winpython provided icon short cut? |
That said, If winpython doesn't seem to fit your environment , you may try with another distribution. |
I read august v2021 version of python-vscode may have change things for good or bad Https://twitter.com/pythonvscode/status/1423710158891352066?s=19 |
Sorry, Was Crashing my way through learning Python :) But on checking I have just noticed that another 1 IDEs (Thonny) are doing the same thing to me and installing packages and dependencies to: |
I agree things have gone south since the days of the Quiche Eaters Will try later to understand your bug with multiple inheritance origin |
Lol, haven't hit that page in a hundred years. Thanks for the smile. |
I just tested the VSCode and is not portable, Writes files to \User\Name\AppData\Roaming\Python39*
Attempted both:
\WPy64-3940\VS Code.exe
\WPy64-3940\t\VSCode\Code.exe (which includes the data directory to make VSCode portable)
I have several dev environments installed and can't have dev paths scattered all over my system due to version conflicts. I generally keep everything in a separate path under C:\Dev\Python39-x86;C:\Dev\Python39-x64\ for example.
I have cleared(Deleted) the created \Roaming* Code and Python directories and tested several times with the same result.
Windows 10 Pro,19043.1151, x64
The text was updated successfully, but these errors were encountered: