languages: Fix Python venv auto-activation for PowerShell 7#46465
Merged
Veykril merged 1 commit intozed-industries:mainfrom Jan 9, 2026
Merged
languages: Fix Python venv auto-activation for PowerShell 7#46465Veykril merged 1 commit intozed-industries:mainfrom
Veykril merged 1 commit intozed-industries:mainfrom
Conversation
This was referenced Jan 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR fixes an issue where Python virtual environments (
venv,uv, etc.) were not automatically activated when opening a terminal using PowerShell 7.Details
ShellKinddistinguishes between the legacy Windows PowerShell (ShellKind::PowerShell) and the newer PowerShell 7 (ShellKind::Pwsh). Previously, the logic inresolve_venv_activation_scriptsonly checked forShellKind::PowerShell, causingactivate.ps1resolution to fail forPwshusers.This change adds
ShellKind::Pwshto the resolution list, mapping it toactivate.ps1just like the legacy PowerShell.Release Notes: