We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Pipsi always uses virtualenv (even on Python 3) to create the virtualenvs packages are installed into.
virtualenv
Normally this isn't a problem, however there seems to an incompatibility with venv when running inside a virtualenv virtualenv.
venv
Related issues:
This is unfortunate since it causes tools installed with pipsi being unable to create other virtualenvs using the builtin venv module.
A solution would be to use venv instead of virtualenv on Python3.
The text was updated successfully, but these errors were encountered:
Seems to be duplicate of #123 and #142 and already fixed in master.
Sorry, something went wrong.
Indeed, appears to be fixed (using b43229d to test): after reinstalling Poetry via pipsi, poetry install now creates a working virtualenv.
poetry install
Any word on when the fix might be released?
pipsi is no longer maintained. You may have better luck with pipx.
No branches or pull requests
Pipsi always uses
virtualenv
(even on Python 3) to create the virtualenvs packages are installed into.Normally this isn't a problem, however there seems to an incompatibility with
venv
when running inside avirtualenv
virtualenv.Related issues:
This is unfortunate since it causes tools installed with pipsi being unable to create other virtualenvs using the builtin
venv
module.A solution would be to use
venv
instead ofvirtualenv
on Python3.The text was updated successfully, but these errors were encountered: