$ /c/Users/builder/AppData/Local/Programs/Python/Python39/Scripts/virtualenv.exe --no-pip --no-setuptools --no-wheel -p /c/Users/builder/AppData/Local/Programs/Python/Python39/python.exe /tmp/tmp.uw7eZfvJIO
$ source /tmp/tmp.uw7eZfvJIO/Scripts/activate
python: command not found
The content of /tmp/tmp.uw7eZfvJIO/Scripts/activate contains VIRTUAL_ENV='C:\tools\msys64\tmp\tmp.uw7eZfvJIO', but it's expected to be VIRTUAL_ENV='/c/tools/msys64/tmp/tmp.uw7eZfvJIO', thus it can't locate python.
I believe the legacy version handles this correctly here:
I am also having this issue. I would be glad to submit a PR if someone could help point me in the right direction. It seems like the creator is correctly building the virtualenv, but we need to modify the path only for setting the VIRTUAL_ENV in the activate script.