EDIT 1
Did some testing and found another more "graceful" way to (at least) update the executable. Let's assume the virtual env was initially created like so
virtualenv -p /path/to/my/python2.7 .venv. The executable can be updated to a specific python version like so: virtualenv --clear -p /path/to/my/python3.6 .venv. Please validate the python symlink in .venv/bin/python is updated using ls -la .venv/bin/python. The old executable(s) will still be in ./venv/bin/.
Note: You need to have the specific target version of python installed.
See this link which explains it well.
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: rmvirtualenv
- This will remove the virtualenv, but leave your project files.
Make a new virtualenv with the Python version you want.
Example: mkvirtualenv -p python3 env-name
You can specify the Python version with the -p flag and version. If
you have a requirements.txt file, you can specify that with -r
requirements.txt
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:
Example: setvirtualenvproject
Please let me/us know if this answer was helpful to you!
