Enhancements to virtualenv
Add two lines to your .bashrc to set the location where the virtual environments should live and the location of the script installed with this package:
export WORKON_HOME=$HOME/.virtualenvs source /usr/local/bin/virtualenvwrapper_bashrc
Run: source ~/.bashrc
A list of environments, empty, is printed.
Run: mkvirtualenv temp
A new environment, temp is created and activated.
This time, the temp environment is included.
Sometimes it is desirable to share installed packages that are not in the system site-pacakges directory and which you do not want to install in each virtualenv. In this case, you could symlink the source into the environment site-packages directory, but it is also easy to add extra directories to the PYTHONPATH by including them in a .pth file inside site-packages using add2virtualenv.
- Check out the source for a big project, such as Django.
- Run: add2virtualenv path_to_source.
- Run: add2virtualenv.
- A usage message and list of current “extra” paths is printed.
virtualenvwrapper adds several hook points you can use to change your settings when creating, deleting, or moving between environments. They are either sourced (allowing them to modify your shell environment) or run as an external program at the appropriate trigger time.
The postactivate script is sourced after the new environment is enabled. $VIRTUAL_ENV refers to the new environment at the time the script runs.
This example script for the PyMOTW environment changes the current working directory and the PATH variable to refer to the source tree containing the PyMOTW source.
pymotw_root=/Users/dhellmann/Documents/PyMOTW cd $pymotw_root PATH=$pymotw_root/bin:$PATH
The predeactivate script is source before the current environment is deactivated, and can be used to disable or clear settings in your environment. $VIRTUAL_ENV refers to the old environment at the time the script runs.
The global postactivate script is sourced after the new environment is enabled and the new environment’s postactivate is sourced (if it exists). $VIRTUAL_ENV refers to the new environment at the time the script runs.
This example script adds a space between the virtual environment name and your old PS1 by making use of _OLD_VIRTUAL_PS1.
PS1="(`basename \"$VIRTUAL_ENV\"`) $_OLD_VIRTUAL_PS1"
The premkvirtualenv script is run as an external program after the virtual environment is created but before the current environment is switched to point to the new env. The current working directory for the script is $WORKON_HOME and the name of the new environment is passed as an argument to the script.
The postmkvirtualenv script is sourced after the new environment is created and activated.
The prermvirtualenv script is run as an external program before the environment is removed. The full path to the environment directory is passed as an argument to the script.
The postrmvirtualenv script is run as an external program after the environment is removed. The full path to the environment directory is passed as an argument to the script.
The function add2virtualenv adds the specified directories to the Python path for the active virtualenv. The directory names passed as argument are added to a path file named virtualenv_path_extensions.pth inside the virtualenv’s site-packages directory. If this file does not exist, it will be created first.
For more details, refer to the column published in the May 2008 issue of Python Magazine: virtualenvwrapper | And Now For Something Completely Different.
- Better error handling in mkvirtualenv.
- Remove bogus VIRTUALENV_WRAPPER_BIN variable.
- Wrap the virtualenv version of deactivate() with one that lets us invoke the predeactivate hooks.
- Fix virtualenvwrapper_show_workon_options for colorized versions of ls and write myself a note so I don’t break it again later.
- Convert test.sh to use true tests with shunit2
- Fix issue #5 by correctly handling symlinks and limiting the list of envs to things that look like they can be activated.
- Check return value of virtualenvwrapper_verify_workon_home everywhere, thanks to Jeff Forcier for pointing out the errors.
- Fix instructions at top of README, pointed out by Matthew Scott.
- Add cdvirtualenv and cdsitepackages, contributed by James Bennett.
- Enhance test.sh.
- Optimize virtualenvwrapper_show_workon_options.
- Add global postactivate hook.
- Pull in fix for colorized ls from Jeff Forcier (b42a25f7b74a).
- Add more hooks for operations to run before and after creating or deleting environments based on changes from Chris Hasenpflug.
- Corrected a problem with change to mkvirtualenv that lead to release 1.8 by using an alternate fix proposed by James in comments on release 1.4.
- Fix for processing the argument list in mkvirtualenv from jorgevargas (BitBucket issue #1)
- Move to bitbucket.org for hosting
- clean up TODO list and svn keywords
- add license section below
- More zsh support (fixes to rmvirtualenv) from Byron Clark.
- Add completion support for zsh, courtesy of Ted Leung.
- Fix some issues with spaces in directory or env names. They still don’t really work with virtualenv, though.
- Added documentation for the postactivate and predeactivate scripts.
- Includes a new .pth management function based on work contributed by James Bennett and Jannis Leidel.
- Includes a fix for a nasty bug in rmvirtualenv identified by John Shimek.
Copyright Doug Hellmann, All Rights Reserved
Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Doug Hellmann not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission.
DOUG HELLMANN DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL DOUG HELLMANN BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.