Fix venv activation for cshell #22852
Merged
Conversation
This file contains 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
karrtikr
added
bug
chrmarti
approved these changes
Feb 5, 2024
chrmarti
approved these changes
Feb 5, 2024
anthonykim1
pushed a commit
that referenced
this pull request
Feb 6, 2024
Closes #22822 Use current shell to figure out whether shell integration is working, even when using fallback shell for getting environment variables.
|
same issue on my Windows vs code and Python latest version; Python virtual environment was successfully activated, even though "(.venv)" indicator may not be present in the terminal prompt. Learn more. using PowerShell
|
|
I am also facing same issue, venv not activating |
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.
Closes #22822
Use current shell to figure out whether shell integration is working, even when using fallback shell for getting environment variables.