Activation prompt with invalid path on Windows Git Bash

[BenediktMaag]

Windows 11, uv 0.2.34 (c681c5a 2024-08-07)

Activating a environment after creating it:

$ uv v
Using Python 3.12.0 interpreter at: C:\Users\MaagB\AppData\Local\Programs\Python\Python312\python.exe
Creating virtualenv at: .venv
Activate with: source .venv\Scripts\activate

$ source .venv\Scripts\activate
bash: .venvScriptsactivate: No such file or directory

Problem:
git bash on windows seems to resolve the escape sequences before making the source call. To properly activate the environment we either need to properly espace the backslash by another backslash:

$ source .venv\Scripts\activate
(tmpinstall)

Or use the Unix Path:
$ source .venv/Scripts/activate
(tmpinstall)

[zanieb]

Thanks for the report!

[charliermarsh]

Do we need to treat Windows Git Bash as its own shell?

[zanieb]

I think it should be sufficient to always use the portable path

[zanieb]

As in #5956

It might make sense to special-case Windows Git Bash still, we see oddities with it.