Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #57860 > unrolled thread
| Started by | Skip Montanaro <skip@pobox.com> |
|---|---|
| First post | 2013-10-28 18:53 -0500 |
| Last post | 2013-10-28 18:53 -0500 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: How do I update a virtualenv? Skip Montanaro <skip@pobox.com> - 2013-10-28 18:53 -0500
| From | Skip Montanaro <skip@pobox.com> |
|---|---|
| Date | 2013-10-28 18:53 -0500 |
| Subject | Re: How do I update a virtualenv? |
| Message-ID | <mailman.1730.1383004893.18130.python-list@python.org> |
> Virtualenvs aren't built to be moved from one Python installation to > another. If you used pip to install your packages (you should), then you > can activate the virtualenv, and run: $ pip freeze > requirements.txt > > Then you can create a new virtualenv using the new Python executable, > activate it, and: $ pip install -r requirements.txt > > This will reinstall all the packages you had installed previously. Even > better is to maintain your own requirements.txt that has just the packages > you need. The "pip freeze" technique will also list packages installed as > dependencies. Hmmm... And my git repo? I imagine I will eventually figure this out, but updating an existing virtualenv in place to adapt to a new version of Python (say, a new micro) or some of its libraries (contents of requirements.txt) seems like it would be a very nice thing to have. Skip
Back to top | Article view | comp.lang.python
csiph-web