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.

Sign up for GitHub

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

Jump to bottom

wrong prompt for conda on powershell #22409

Closed
ghost opened this issue Nov 2, 2023 · 1 comment
Closed

wrong prompt for conda on powershell #22409

ghost opened this issue Nov 2, 2023 · 1 comment
Assignees
@karrtikr
Labels
info-needed Issue requires more information from poster triage-needed Needs assignment to the proper sub-team

Comments

@ghost
Copy link

ghost commented Nov 2, 2023 •
edited by ghost
Loading

When launching a powershell, vs code python plugin uses a wrong prompt for miniconda
It should be C:/Miniconda3/Scripts/activate.bat instead of C:/Miniconda3/Scripts/activate

the currently used one is for Linux with /bin/sh, but the tested enviroment is on windows with powershell

this bug is really annoying as it requires manually typing the correct prompt and then conda activate or set C:/Miniconda3/Scripts/activate.ps1 to be loaded automatically with conda init

[vscode-python]
v2023.20.0

[vscode]
version: 1.83.1 (user setup)
commit: f1b07bd25dfad64b0167beb15359ae573aecd2cc
date: 2023-10-10T23:48:05.904Z
Electron: 25.8.4
ElectronBuildId: 24154031
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Windows_NT x64 10.0.22621
@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Nov 2, 2023
@ghost ghost changed the title vs code python plugin uses a wrong prompt for miniconda on powershell wrong prompt for miniconda on powershell Nov 2, 2023
@ghost ghost changed the title wrong prompt for miniconda on powershell wrong prompt for conda on powershell Nov 2, 2023
@karrtikr
Copy link

karrtikr commented Nov 2, 2023

Your issue should be addressed with #11039, where we stop using activation commands altogether.

  • Add the following to User settings and reload window: 
    "python.experiments.optInto": ["pythonTerminalEnvVarActivation"]

@karrtikr karrtikr closed this as not planned Won't fix, can't repro, duplicate, stale Nov 2, 2023
@github-actions github-actions bot added the info-needed Issue requires more information from poster label Nov 2, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@karrtikr karrtikr

Labels
info-needed Issue requires more information from poster triage-needed Needs assignment to the proper sub-team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@karrtikr