Change Python Version in an Existing Virtualenv
September 10, 2016
This is a short article describing how you can change the Python interpreter version in an existing virtualenv. If you start working on a project and realize you wish you started with Python 2, or you started with version 2 and wish you started with version 3, this can easily be change.
In this article I use virtualenvwrapper for managing Python virtualenvs.
The first thing to consider is using two directory locations for your virtualenvs. One for your libraries and packages and a different location for your project files. This is the key for being able to disconnect and change your Python interpreter. Keeping your project files separate makes version control a little easier too.
Virtualenvwrapper comes with some convenient commands for managing your virtualenvs.
To change your Python version:
Deactivate your current environment session.
If you have many packages or libraries installed, it would be a good idea to make a requirements.txt file. Remember to edit version as necessary.
Remove the virtualenv with the wrapper command:
This will remove the virtualenv, but leave your project files.
Make a new virtualenv with the Python version you want.
mkvirtualenv -p python3 env-name
You can specify the Python version with the
-pflag and version. If you have a requirements.txt file, you can specify that with
Now bind your new virtualenv to your project directory. You can specify the full paths, but it is easier to have your new virtualenv activated and be in your project directory. Then, run the command:
Read the docs for more details: