-
-
Notifications
You must be signed in to change notification settings - Fork 528
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 fails to create py27 virtualenv - installs packages to system site packages #1435
Comments
If I remove
|
I was able to replicate the issue in an isolated Docker image with this Dockerfile:
In doing so, I learned that tox-pip-version is implicated also. |
I suggest this issue is a major blocker as the use of |
I've observed that removing either of tox-venv or tox-pip-version bypasses the error. |
I see this as a bug of either tox-venv or tox-pip-version. This will be provided internally with #1400, not to be released though until early next year as for now I'm busy with pypa/virtualenv#1377 |
…hout requiring tox-run-command (and the trouble that adds).
Attempting to run tox against Python 2.7, I find that all commands are run in the system and not in the environment.
Tox is installed thus:
As you can see, I've used pipx to install tox, so it's created in a pyvenv in ~/.local/pipx/tox.
I create this tox.ini:
I then run tox:
And the env isn't working:
If I had specified deps in the tox.ini, they would have been installed into my system site packages.
The text was updated successfully, but these errors were encountered: