/py-virtualenv, Virtual Python Environment builder
15.1.0, Package name:
py27-virtualenv-15.1.0, Maintainer: pkgsrc-users
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
everything into /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).
Required to run:
] Required to build:
Master sites: SHA1:
Version history: (Expand)
- (2016-11-29) Updated to version: py27-virtualenv-15.1.0
- (2016-08-19) Updated to version: py27-virtualenv-15.0.3
- (2016-06-14) Updated to version: py27-virtualenv-15.0.2nb1
- (2016-05-30) Updated to version: py27-virtualenv-15.0.2
- (2016-04-14) Updated to version: py27-virtualenv-15.0.1
- (2016-03-08) Updated to version: py27-virtualenv-15.0.0
CVS history: (Expand)