-
Notifications
You must be signed in to change notification settings - Fork 26
Problem using virtualenvwrapper on Windows with git bash #124
Copy link
Copy link
Open
Description
I found two issues that I want to report. I am sorry that I do not have the time to submit a pull request.
- In the doc, it mentions that to use on Windows with MSYS that the MSYS_HOME variable needs to be set.
In the Installation section under MSYS
export MSYS_HOME=/c/msys/1.0
On my system that needs to be
export MSYS_HOME=/c/msys64/usr
because there is no bin directory under msys64 so it needs/usrto be able to fins sh.exe in user_scripts.py _get_sys_shell()
This really just a doc problem, but I did have to go looking to find out why running postmkvirtualenv was failing in mkproject.
NOTE: I do think that MSYS_HOME as the variable name is not reflecting that it is needed for virtualenvwrapper.
- There is a path issue when trying to connect the virtualenv to the project in mkproject. The issue is that python on windows, even running under bash uses Windows/non-posix style paths. This often leads to mixing of separators and the drive: prefix.
My fix was to remove the use of python to convert paths to absolute and expand vars, etc. Instead I switched to readlink. In the two functions: virtualenvwrapper_expandpath and virtualenvwrapper_absolutepath I just changed the the single line modifying the filepath variable.
<< "$VIRTUALENVWRAPPER_PYTHON" -c "import os,sys; ...
>> readlink -f "$1"
I have confirmed that it works on MSYS and Debian.
Thanks for continuing to support the project!
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels