Replies: 1 comment
-
The option still exists, but it requires an existing virtualenv. It was too easy to accidentally create a virtualenv when making a typo in the path. You first have to use I hope this explanation helps you. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I recently upgraded to devpi-client 6.x and my existing workflow of using devpi install with the venv option failed.
I am hoping to learn the reason behind the removal of the --venv option from install and what is the correct way to achieve the same effect as per the <6.0 version of devpi-client
Thank you
Beta Was this translation helpful? Give feedback.
All reactions