Parents (Total: 8)

The searched file hash is included in 8 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	BDA88FC7BE810CDB5A9F44A40E3C0DF0
PackageArch	noarch
PackageDescription	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.4/site-packages (or whatever your platforms standard location is), its easy to end up in a situation where you unintentionally upgrade an application that shouldnt 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 cant 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 doesnt share libraries with other virtualenv environments (and optionally doesnt use the globally installed libraries either).
PackageMaintainer	https://bugs.opensuse.org
PackageName	python2-virtualenv
PackageRelease	lp151.1.1
PackageVersion	16.1.0
SHA-1	FB76A50838B2FF8F44D06B021D9D4960052D4BE5
SHA-256	6A35B1A186AFFBC5837BDD7BE247478E252677554F55E03CB83C8E6BB60C0D68

Key	Value
MD5	CC8EF4D23CFFC124C7BFE1111E29E972
PackageArch	noarch
PackageDescription	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.4/site-packages (or whatever your platforms standard location is), its easy to end up in a situation where you unintentionally upgrade an application that shouldnt 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 cant 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 doesnt share libraries with other virtualenv environments (and optionally doesnt use the globally installed libraries either).
PackageMaintainer	https://bugs.opensuse.org
PackageName	python3-virtualenv
PackageRelease	lp152.2.4
PackageVersion	16.1.0
SHA-1	9D40E6C8CE6FF0695F3F6BF591F49743157D7D32
SHA-256	FA2570479192876F79990B050FD03FFD2DCA7937E044B8BD5AD39ACE2076110C

Key	Value
MD5	754ADF75CE2D3B3536C6A18D6B78E529
PackageArch	noarch
PackageDescription	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.4/site-packages (or whatever your platforms standard location is), its easy to end up in a situation where you unintentionally upgrade an application that shouldnt 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 cant 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 doesnt share libraries with other virtualenv environments (and optionally doesnt use the globally installed libraries either).
PackageMaintainer	https://bugs.opensuse.org
PackageName	python2-virtualenv
PackageRelease	lp152.2.4
PackageVersion	16.1.0
SHA-1	2D3FA583EEB95D9022F47F14BF24512E2D633065
SHA-256	E626DDC897AB37BF665C94F95E2FF5E50052AE1C29D018E2525F5A3C8434D5F3

Key	Value
MD5	A20ACA0CF3EEEFE128359D22BD13B1FD
PackageArch	noarch
PackageDescription	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.4/site-packages (or whatever your platforms standard location is), its easy to end up in a situation where you unintentionally upgrade an application that shouldnt 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 cant 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 doesnt share libraries with other virtualenv environments (and optionally doesnt use the globally installed libraries either).
PackageName	python2-virtualenv
PackageRelease	lp150.2.2
PackageVersion	16.7.5
SHA-1	318E095082506419391EE586101D587F486CB05C
SHA-256	4901401CC5714E3A04D0FD97E81FDAFD0FEA9E736E5B91C9BC40B449DE340F34

Key	Value
MD5	C4B1619A94002622A75B5854D2FE5DC6
PackageArch	noarch
PackageDescription	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.4/site-packages (or whatever your platforms standard location is), its easy to end up in a situation where you unintentionally upgrade an application that shouldnt 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 cant 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 doesnt share libraries with other virtualenv environments (and optionally doesnt use the globally installed libraries either).
PackageMaintainer	https://bugs.opensuse.org
PackageName	python3-virtualenv
PackageRelease	lp151.1.1
PackageVersion	16.1.0
SHA-1	027549FC2DCE69ED2B23BCE9FFDD3A4C899E80D3
SHA-256	51D3DA08AF325292DA108520B369957F3E02291F1D651E5809B4FE9F806FC774

Key	Value
MD5	FF7DC4832E0B48EF8D1DA6D17861FFD6
PackageArch	noarch
PackageDescription	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.4/site-packages (or whatever your platforms standard location is), its easy to end up in a situation where you unintentionally upgrade an application that shouldnt 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 cant 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 doesnt share libraries with other virtualenv environments (and optionally doesnt use the globally installed libraries either).
PackageMaintainer	https://www.suse.com/
PackageName	python2-virtualenv
PackageRelease	1.13
PackageVersion	16.1.0
SHA-1	2D1D9858B91763F06339BA1EDF499D7493460272
SHA-256	63976FA3EEB62662C95EE5580E6EF33A2B6E8E311F2BBDCBC5A733A4516DC955

Key	Value
MD5	8D7C6E97DC67779DDD919A14540FFEB2
PackageArch	noarch
PackageDescription	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.4/site-packages (or whatever your platforms standard location is), its easy to end up in a situation where you unintentionally upgrade an application that shouldnt 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 cant 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 doesnt share libraries with other virtualenv environments (and optionally doesnt use the globally installed libraries either).
PackageMaintainer	https://www.suse.com/
PackageName	python3-virtualenv
PackageRelease	1.13
PackageVersion	16.1.0
SHA-1	FA10D226399DB304BF01DD06B23F722F9923BE7B
SHA-256	204E1E5C770DF36D5A4352717D7F4173121321BBF6567C8E5452B5F77BC40FD1

Key	Value
MD5	ACB098BB25F2916F8B3AD7A27E0D3010
PackageArch	noarch
PackageDescription	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.4/site-packages (or whatever your platforms standard location is), its easy to end up in a situation where you unintentionally upgrade an application that shouldnt 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 cant 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 doesnt share libraries with other virtualenv environments (and optionally doesnt use the globally installed libraries either).
PackageName	python3-virtualenv
PackageRelease	lp150.2.2
PackageVersion	16.7.5
SHA-1	0F996A3CD5BA55F1E9125FEACFF6673EEB099A11
SHA-256	45D35DFDCBB39BDB7823CF06A1AAEEB025CC853FB90975FF59363E1803D544AB