microsoft / microsoft/vscode-python-environments
The automatic activation mechanism has been damaged
@anthonykim1 arbeitet bereits daran.
Seit 05.2.2026.
- Vorherrschende Sprache
- TypeScript
- Sterne
- 138
- Forks
- 62
- Ø Merge
- 1 T. 4 Std.
- Gemergte PRs (30 T.)
- 35
Beschreibung
Before, my terminal in VSCode will keep conda env activated automatically without `conda init`, when I choose a python interpreter.
But now, it break my python env auto activation. When I use code runner to run a python script in a new terminal, the terminal don't activate in the desired python interpreter, but use the default base env of conda. **I want to solve how can I keep workshop's terminal in desired python interpreter env when as soon as I open it without using any commands.**
**My core problem is the terminal don't keep in the workshop's python interpreter env, but when I open terminal, it run `Anaconda/Scripts/activate` to activate env, which report "CondaError: Run 'conda init' before 'conda activate'", but i don't want use `conda init` to pollute my terminal.**
I'm not a professional developer, my description might be somewhat inappropriate. For more information please ask me.
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Bewertung
Dieses Issue wurde noch nicht bewertet.