Fix where activation goes missing after user modifying rc scripts#880
Merged
anthonykim1 merged 2 commits intomainfrom Oct 1, 2025
Merged
Fix where activation goes missing after user modifying rc scripts#880anthonykim1 merged 2 commits intomainfrom
anthonykim1 merged 2 commits intomainfrom
Conversation
Tyriar
approved these changes
Oct 1, 2025
eleanorjboyd
pushed a commit
to eleanorjboyd/vscode-python-environments
that referenced
this pull request
Oct 8, 2025
…crosoft#880) Resolves: microsoft#865 If user modifies already existing shell profile script needed for shell startup, they get stuck into not activating state because they still have auto activation guard, which blocks shell integration from core from activating. This also means because they have wrong env var in profile script, it won't activate there either. We should better track this, and properly clean up profile script when relying on shell integration for activation. /cc @karthiknadig
NguyenCuong1989
referenced
this pull request
in NguyenCuong1989/vscode-python-environments
Oct 23, 2025
Resolves: microsoft/vscode-python-environments#865 If user modifies already existing shell profile script needed for shell startup, they get stuck into not activating state because they still have auto activation guard, which blocks shell integration from core from activating. This also means because they have wrong env var in profile script, it won't activate there either. We should better track this, and properly clean up profile script when relying on shell integration for activation. /cc @karthiknadig
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
2 participants
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.
Resolves: #865
If user modifies already existing shell profile script needed for shell startup, they get stuck into not activating state because they still have auto activation guard, which blocks shell integration from core from activating.
This also means because they have wrong env var in profile script, it won't activate there either.
We should better track this, and properly clean up profile script when relying on shell integration for activation.
/cc @karthiknadig