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

Saving python path #16582

Closed
richtera opened this issue Jun 29, 2021 · 2 comments
Closed

Saving python path #16582

richtera opened this issue Jun 29, 2021 · 2 comments

Comments

@richtera
Copy link

Issue Type: Feature Request

Currently the python path is being saved to .vscode/settings.json
That's not very portable because many times the python path contains the user directory path. I might be a lot better if the the python is from a conda or pyenv to store the name of the environment instead. At least then the user can create the same named environment on each of their machines and the settings.json file would no longer need to change each time. Right now one has to continuously stash and stash apply this file to exclude it from normal commits.

VS Code version: Code 1.57.1 (507ce72a4466fbb27b715c3722558bb15afa9f48, 2021-06-17T13:28:07.755Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No
Remote OS version: Linux x64 4.19.128-microsoft-standard
Remote OS version: Linux x64 4.19.128-microsoft-standard
Remote OS version: Linux x64 4.19.128-microsoft-standard
Remote OS version: Linux x64 4.19.128-microsoft-standard
Remote OS version: Linux x64 4.19.128-microsoft-standard

@sbatten sbatten transferred this issue from microsoft/vscode Jun 29, 2021
@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Jun 29, 2021
@brettcannon
Copy link
Member

We have an experiment that just rolled out to 50% of users which stops saving to settings.json for your Python environment path, so we will no longer be doing this shortly.

Closing as a duplicate of #2125 .

@luabud
Copy link
Member

luabud commented Jun 30, 2021

Also worth mentioning that this experience is already available in our insiders build 😊

@karthiknadig karthiknadig removed the triage-needed Needs assignment to the proper sub-team label Jul 7, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 19, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants