-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Document that Anaconda users should launch VS Code from an activated conda environment #3481
Comments
@luabud / @brettcannon - Looks like if you use a conda prompt, navigate to your directory, and use code . to launch VS Code it ensures the terminal has an activated environment, but it doesn't look like that carries over to the selected interpreter. Is there a way to get that to happen from the command line too? Or is that a step folks will still need to take once VS Code is up? |
@JoshuaPartlow it's a possibility. I've opened microsoft/vscode-python#10668 about the idea. @luabud should we hold off on documenting this until we have such support in place? |
@brettcannon ugh sorry, I completely missed this. I think it's still fair to document that this is a workaround that folks can try, and then add that they can select the interpreter by clicking on the status bar (or running the command). This workaround doesn't work on remote scenarios though 😟 |
Have a PR in progress that adds this as a note to the conda environment section of the environments topic. |
Update included in above PR. If we get to microsoft/vscode-python#10668 let me know or reopen the issue. |
To make the experience better for conda users, we should advise them that they should launch VS Code from the activated conda environment they are going to be using. That way the environment is already set up from a shell perspective.
/cc @luabud @microsoft/pvsc-team
The text was updated successfully, but these errors were encountered: