New submission from Mo <moabrah...@dashavoo.com>:
When creating a virtual environment on Windows from git-bash (using python -m venv), VIRTUAL_ENV in the activate script is set using a windows style path (C:\some\path) instead of the bash style (/c/some/path). This means the system python and pip get used, despite the user thinking they are working in a venv after sourcing activate. As activate is a bash script, the paths in it should always be in the bash style, regardless of platform. This is described in a stack overflow issue here: https://stackoverflow.com/questions/57758841/windows-virtualenv-created-via-gitbash-using-system-python I have confirmed the behaviour in 3.7.3, 3.7.4, 3.7.5 and 3.8.0. ---------- components: Windows messages: 355333 nosy: Mo, paul.moore, steve.dower, tim.golden, zach.ware priority: normal severity: normal status: open title: The activate script in Windows is not correct for venvs created in git-bash type: behavior versions: Python 3.7, Python 3.8 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue38583> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
