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

Terminal Python environment activation command exception #19731

Closed
shaoqx opened this issue Jul 25, 2022 · 2 comments
Closed

Terminal Python environment activation command exception #19731

shaoqx opened this issue Jul 25, 2022 · 2 comments
Assignees
Labels
area-environments Features relating to handling interpreter environments bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster triage-needed Needs assignment to the proper sub-team

Comments

@shaoqx
Copy link

shaoqx commented Jul 25, 2022

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version:1.69.2 (user setup) - 3b889b090b5ad5793f524b5d1d39fda662b96a2a
    Datetime: 2022-07-18T16:12:52.460Z
    Electron: 18.3.5
    Chromium: 100.0.4896.160
    Node.js: 16.13.2
    V8: 10.0.139.17-electron.0
  • OS: Windows_NT x64 10.0.19044

Steps to Reproduce:
"I was using SSH-Remote to use a workspace on a Linux machine"

  1. My python environment was set to be a conda environment and conda base is not activated by default in my shell
  2. The activation command recently changed to source activate xxxxx, which do not work if base is not activated forheaded. I suggest changing back to the old way
@karthiknadig karthiknadig transferred this issue from microsoft/vscode Aug 24, 2022
@karthiknadig karthiknadig removed their assignment Aug 24, 2022
@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Aug 24, 2022
@karthiknadig karthiknadig added area-environments Features relating to handling interpreter environments bug Issue identified by VS Code Team member as probable bug labels Aug 25, 2022
@karrtikr
Copy link

We use source activate if the shell has not been initialized first. Use conda init --all and let us know if the problem still happens.

@karrtikr karrtikr added the info-needed Issue requires more information from poster label Aug 25, 2022
@shaoqx
Copy link
Author

shaoqx commented Aug 25, 2022

Somehow it is changed back to the old way source /path/to/env/activate after an update so I'm happy now :)

@shaoqx shaoqx closed this as completed Aug 25, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 25, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-environments Features relating to handling interpreter environments bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster triage-needed Needs assignment to the proper sub-team
Projects
None yet
Development

No branches or pull requests

4 participants