fix(virtualenv): improve virtual environment activation logic #204
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.
This fix addresses an issue where virtual environments were not activating when opening a terminal directly in a project directory or restarting the shell e.g.
exec zsh
in the project directory.for some reason when reloading the shell it would set the .venv bin below the regular python bin in $PATH. This added function will doublecheck if the .venv path is set on top when the shell reloads in the project directory containing the .venv