You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That's a cool plugin and all, but it doesn't seem to support virtualenvs that you want to move from one parent to another, preserving the env's name. For example, say I have 3.6.4 installed and a virtualenv installed under it (/usr/local/Cellar/pyenv/1.2.3/versions/3.6.4/envs/my-venv). Now I install 3.6.5 and because I want my-env to use that instead, I want it to be at /usr/local/Cellar/pyenv/1.2.3/versions/3.6.5/envs/my-venv. Is there a process for making that happen?
While working on different library version it would be extremely helpful to be able to clone an existing virtualenv.
Right now what I do is:
pip freeze > requirements.txt
in the current virtualenvpyenv virtualenv ...
pyenv shell newvirtualenv
pip install -r requirements.txt
Not too bad, but it could be easier.
The text was updated successfully, but these errors were encountered: