Skip to content
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

Feature suggestion: clone virtualenv to new env #6

Closed
al3xandru opened this issue Nov 21, 2013 · 2 comments
Closed

Feature suggestion: clone virtualenv to new env #6

al3xandru opened this issue Nov 21, 2013 · 2 comments

Comments

@al3xandru
Copy link

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:

  1. pip freeze > requirements.txt in the current virtualenv
  2. pyenv virtualenv ...
  3. pyenv shell newvirtualenv
  4. pip install -r requirements.txt

Not too bad, but it could be easier.

@yyuu
Copy link
Collaborator

yyuu commented Nov 22, 2013

@yyuu yyuu closed this as completed Nov 22, 2013
@neverfox
Copy link

neverfox commented Apr 1, 2018

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants