Skip to content

Refactor environment extension activation checks to use shouldEnvExtHandleActivation function#25895

Merged
edvilme merged 1 commit intomicrosoft:mainfrom
eleanorjboyd:tart-toucan
Apr 15, 2026
Merged

Refactor environment extension activation checks to use shouldEnvExtHandleActivation function#25895
edvilme merged 1 commit intomicrosoft:mainfrom
eleanorjboyd:tart-toucan

Conversation

@eleanorjboyd
Copy link
Copy Markdown
Member

Problem
Fixes #1284

When the Python Environments extension (ms-python.vscode-python-envs) is installed but python.useEnvironmentsExtension is not explicitly set, users see two interpreter status bar items — one from each extension.

Root Cause
The interpreter display in InterpreterDisplay used useEnvExtension() to decide whether to create/show its status bar. That function requires python.useEnvironmentsExtension to be explicitly true (defaults to false). Meanwhile, the envs extension activates whenever the setting is not explicitly false — treating unset/undefined as enabled.

@edvilme edvilme added the bug Issue identified by VS Code Team member as probable bug label Apr 15, 2026
@edvilme edvilme enabled auto-merge (squash) April 15, 2026 22:17
@edvilme edvilme merged commit 437afb5 into microsoft:main Apr 15, 2026
49 of 50 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Issue identified by VS Code Team member as probable bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Integrated Terminal Window becomes active

3 participants