virtualenv is a tool to create isolated Python environments.
The basic problem being addressed is one of dependencies and versions,
and indirectly permissions. Imagine you have an application that
needs version 1 of LibFoo, but another application requires version
2. How can you use both these applications? If you install
/usr/lib/python2.7/site-packages (or whatever your
platform's standard location is), it's easy to end up in a situation
where you unintentionally upgrade an application that shouldn't be
Or more generally, what if you want to install an application and leave it be? If an application works, any change in its libraries or the versions of those libraries can break the application.
Also, what if you can't install packages into the global
site-packages directory? For instance, on a shared host.
In all these cases,
virtualenv can help you. It creates an
environment that has its own installation directories, that doesn't
share libraries with other virtualenv environments (and optionally
doesn't access the globally installed libraries either).
.. toctree:: :maxdepth: 2 installation userguide reference development changes
Other Documentation and Links
- Blog announcement of virtualenv.
- James Gardner has written a tutorial on using virtualenv with Pylons.
- Chris Perkins created a showmedo video including virtualenv.
- Doug Hellmann's virtualenvwrapper is a useful set of scripts to make your workflow with many virtualenvs even easier. His initial blog post on it. He also wrote an example of using virtualenv to try IPython.
- Pew is another wrapper for virtualenv that makes use of a different activation technique.
- Using virtualenv with mod_wsgi.
- virtualenv commands for some more workflow-related tools around virtualenv.
- PyCon US 2011 talk: Reverse-engineering Ian Bicking's brain: inside pip and virtualenv. By the end of the talk, you'll have a good idea exactly how pip and virtualenv do their magic, and where to go looking in the source for particular behaviors or bug fixes.
Compare & Contrast with Alternatives
There are several alternatives that create isolated environments:
workingenv(which I do not suggest you use anymore) is the predecessor to this library. It used the main Python interpreter, but relied on setting
$PYTHONPATHto activate the environment. This causes problems when running Python scripts that aren't part of the environment (e.g., a globally installed
bzr). It also conflicted a lot with Setuptools.
virtual-python is also a predecessor to this library. It uses only symlinks, so it couldn't work on Windows. It also symlinks over the entire standard library and global
site-packages. As a result, it won't see new additions to the global
This script only symlinks a small portion of the standard library into the environment, and so on Windows it is feasible to simply copy these files over. Also, it creates a new/empty
site-packagesand also adds the global
site-packagesto the path, so updates are tracked separately. This script also installs Setuptools automatically, saving a step and avoiding the need for network access.
zc.buildout doesn't create an isolated Python environment in the same style, but achieves similar results through a declarative config file that sets up scripts with very particular packages. As a declarative system, it is somewhat easier to repeat and manage, but more difficult to experiment with.
zc.buildoutincludes the ability to setup non-Python systems (e.g., a database server or an Apache instance).
I strongly recommend anyone doing application development or deployment use one of these tools.