> 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 -- https://mail.python.org/mailman/listinfo/python-list
