Search results

Feature Request: activate default project python/conda environment when launching a task

triage-needed

Status: Open.

#1053 In microsoft/vscode-python-environments;

· albertino87 opened on Dec 10, 2025

Should use onDidChangeTerminalShellIntegration event instead of polling

area-activationIssue related to activation. Root cause can be from interpreter selection or activation in terminalIssue related to activation. Root cause can be from interpreter selection or activation in terminal

area-terminalEnvironment extension specific terminal issues.Environment extension specific terminal issues.

debt

Status: Open.

#1047 In microsoft/vscode-python-environments;

· anthonykim1 opened on Dec 9, 2025

·  

December / January 2026

Remove stale globalPersistent

area-activationIssue related to activation. Root cause can be from interpreter selection or activation in terminalIssue related to activation. Root cause can be from interpreter selection or activation in terminal

area-terminalEnvironment extension specific terminal issues.Environment extension specific terminal issues.

debt

Status: Open.

#1045 In microsoft/vscode-python-environments;

· anthonykim1 opened on Dec 9, 2025

·  

December / January 2026

documentation for searchPaths

documentationImprovements or additions to documentationImprovements or additions to documentation

needs proposal

Status: Open.

#1041 In microsoft/vscode-python-environments;

· eleanorjboyd opened on Dec 8, 2025

open terminal from global python activates wrong environment

bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bug

needs PR

Status: Open.

#1035 In microsoft/vscode-python-environments;

· eleanorjboyd opened on Dec 8, 2025

[Bug] Conda Environments not found (windows)

bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bug

triage-needed

Status: Open.

#1034 In microsoft/vscode-python-environments;

· riedgar-ms opened on Dec 8, 2025

Issues working on workspaces with multiple components subfolders, each with it's own venv.

triage-needed

Status: Open.

#1032 In microsoft/vscode-python-environments;

· Carbaz opened on Dec 6, 2025

launching a local integrated terminal from wsl will look for linux location for venv

bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bug

Status: Open.

#1027 In microsoft/vscode-python-environments;

· amunger opened on Dec 4, 2025

.\vscode-python\deactivate.ps1 in PowerShell_profile.ps1 breaks activation

bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bug

needs spike

Status: Open.

#1026 In microsoft/vscode-python-environments;

· amunger opened on Dec 4, 2025

Python env auto-activation regression: Terminal no longer activates unless legacy settings are enabled

triage-needed

Status: Open.

#1025 In microsoft/vscode-python-environments;

· JVSCHANDRADITHYA opened on Dec 4, 2025

Consider caching for shellStartup profiles

debt

needs proposal

Status: Open.

#1023 In microsoft/vscode-python-environments;

· anthonykim1 opened on Dec 3, 2025

·  

December / January 2026

Add tests for shell startup activation

debt

needs PR

Status: Open.

#1019 In microsoft/vscode-python-environments;

· anthonykim1 opened on Dec 3, 2025

·  

December / January 2026