[3.13] gh-125398: Convert paths in venv activate script when using Git Bash under Windows (GH-125399) #125733
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.
With #112508 the check to converts paths when running on Windows was changed from using the non-posix environment variable
$OSTYPEto usingunameinstead.However this missed the fact that when running under Git Bash on Windows, uname reports
MINGW*($OSTYPEis stillmsys).This results in
$PATHbeing set to something likeD:\a\github-actions-shells\github-actions-shells\venv/Scripts:…, instead of/d/a/github-actions-shells/github-actions-shells/venv/Scripts.Notably, the Git Bash is the bash shell that’s used for GitHub Actions Windows runners, and ships with VSCode.
(cherry picked from commit 2a378db)
Co-authored-by: Julien julien@caffeine.lu