Skip to content

Experiment - DeprecatePythonPath #13045

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

Closed
yspreen opened this issue Jul 19, 2020 · 4 comments
Closed

Experiment - DeprecatePythonPath #13045

yspreen opened this issue Jul 19, 2020 · 4 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug investigating We are looking into the cause of the issue verified Verification succeeded
Milestone

Comments

@yspreen
Copy link

yspreen commented Jul 19, 2020

How am I supposed to set the pythonPath now, on a repository basis? Do you expect us to manually specify the python path on every machine now? If so, why would this backward step be made?

@yspreen yspreen added triage-needed Needs assignment to the proper sub-team bug Issue identified by VS Code Team member as probable bug labels Jul 19, 2020
@karrtikr
Copy link

Please have a look at the wiki for more details on why such a step was made. We'll get back to you soon.

@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Jul 20, 2020
@yspreen
Copy link
Author

yspreen commented Jul 20, 2020

I did read through that article before posting here @karrtikr. However, I could not find a replacement for the repo-level configuration of this setting.

@karrtikr
Copy link

@yspreen You're right. The interpreter path setting now cannot be commited to a repository, as it's now stored in a VSCode storage.

I pointed you to the wiki as you asked for the reason we had to remove interpreter path from settings. One of them was this: #7805. Which basically meant we cannot have the setting value stored inside the workspace folder for security reasons.

You're welcome to suggest us your ideas regarding any other solution you may think of.

@karthiknadig karthiknadig added investigating We are looking into the cause of the issue and removed triage labels Sep 15, 2020
@karrtikr
Copy link

You can now use python.defaultInterpreterPath to share the settings at repo level. The wiki has been updated accordingly.

@karrtikr karrtikr added this to the October 2021 milestone Oct 22, 2021
@karrtikr karrtikr added the verified Verification succeeded label Oct 25, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug investigating We are looking into the cause of the issue verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

4 participants