New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tox uses wrong virtualenv PATH under MSYS #1982
Labels
bug:normal
affects many people or has quite an impact
Comments
jschwartzentruber
added
the
bug:normal
affects many people or has quite an impact
label
Mar 29, 2021
PRs are welcomed. |
jschwartzentruber
added a commit
to jschwartzentruber/tox
that referenced
this issue
Mar 29, 2021
…on Windows. MSYS2 prefers a Linux filesystem layout, but is otherwise a native Windows interpreter. Fixes tox-dev#1982
jschwartzentruber
added a commit
to jschwartzentruber/tox
that referenced
this issue
Apr 1, 2021
…on Windows. MSYS2 prefers a Linux filesystem layout, but is otherwise a native Windows interpreter. Fixes tox-dev#1982
jschwartzentruber
added a commit
to jschwartzentruber/tox
that referenced
this issue
Apr 1, 2021
…on Windows. MSYS2 prefers a Linux filesystem layout, but is otherwise a native Windows interpreter. Fixes tox-dev#1982
gaborbernat
changed the title
Tox uses wrong virtualenv PATH under MSYS
tox uses wrong virtualenv PATH under MSYS
Apr 5, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
tox assumes that all Windows installations use "{ENV}\Scripts" as the installation folder. This isn't true for MSYS, which uses "{ENV}\bin". If I patch
TestenvConfig.get_envbindir()
to return "bin" instead of "Scripts", tox uses the correct interpreter.I believe an exception is needed if
MSYSTEM
is set in the environment (or I don't know if there's a more "proper" way to detect MSYS), similar to the exception that exists in that function for PyPy.This was already mentioned in msys2/MINGW-packages#7014 and #1648, but those dealt with other upstream packaging issues, and I see no tox issue regarding this specific problem.
Steps to reproduce
Install msys2 and in its
bash
shell, runpacman -S mingw-w64-x86_64-python mingw-w64-x86_64-python-pip mingw-w64-x86_64-python-wheel
, then install latest tox using pip.The project I've experienced this on is fuzzfetch. Just clone and run
tox -e py38
.The text was updated successfully, but these errors were encountered: