Closed chrysle closed 1 year ago
This is a Debian downstream issue, and that's not us.
Just wondering: If it's Debian, and the issue can't be fixed, why shouldn't the docs contain a warning?
Because ideally should be a Debian issue and documentation 🤔
PS. Debian is horrible for Python development 🤷
Note we encourage users to install this tool via pipx or in a venv, so if you run issue you're already not following our documentation 🤔 so you're in a unsupported world.
See https://virtualenv.pypa.io/en/latest/installation.html#via-pip
Alternatively you can install it within the global Python interpreter itself (perhaps as a user package via the --user flag). Be cautious if you are using a python install that is managed by your operating system or another package manager. pip might not coordinate with those tools, and may leave your system in an inconsistent state.
Is what you're running into.
PS. Debian is horrible for Python development
Note that I'm using Ubuntu ;-)
Note we encourage users to install this tool via pipx or in a venv, so if you run issue you're already not following our documentation thinking so you're in a unsupported world.
Yes, maybe you're right.
Note that I'm using Ubuntu ;-)
Which is a Debian derivative so is the same 😊
Issue
I had the debian package
python3-virtualenv
installed (as a dependency to the packagetox
) and tried to invoketox
in the directory of the cloned source code ofvirtualenv
. However, this failed with an error message:I had to remove the
tox
package and reinstall viapip
.Environment
Provide at least:
pip list
of the host python wherevirtualenv
is installed: