pkgsrc/devel/py-virtualenv/distinfo

$NetBSD: distinfo,v 1.10 2014/05/20 08:49:26 wiz Exp $

SHA1 (virtualenv-1.11.6.tar.gz) = d3f8e94bf825cc999924e276c8f1c63b8eeb0715
RMD160 (virtualenv-1.11.6.tar.gz) = 641bb4e84031f4e5d160ac87a2e4c1dbc7e85ba5
Size (virtualenv-1.11.6.tar.gz) = 1610581 bytes
Update to 1.11.6: 1.11.6 (2014-05-16) ~~~~~~~~~~~~~~~~~~~ * Updated setuptools to 3.6 * Updated pip to 1.5.6 2014-05-20 10:49:26 +02:00			$NetBSD: distinfo,v 1.10 2014/05/20 08:49:26 wiz Exp $
Import py-virtualenv-1.8.2 as devel/py-virtualenv. 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 upgraded. 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). 2012-10-07 00:23:22 +02:00
Update to 1.11.6: 1.11.6 (2014-05-16) ~~~~~~~~~~~~~~~~~~~ * Updated setuptools to 3.6 * Updated pip to 1.5.6 2014-05-20 10:49:26 +02:00			`SHA1 (virtualenv-1.11.6.tar.gz) = d3f8e94bf825cc999924e276c8f1c63b8eeb0715`
			`RMD160 (virtualenv-1.11.6.tar.gz) = 641bb4e84031f4e5d160ac87a2e4c1dbc7e85ba5`
			`Size (virtualenv-1.11.6.tar.gz) = 1610581 bytes`