Parents (Total: 3)

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

Key	Value
MD5	64E862CA029DBCF00BEDF1709E1BF62F
PackageArch	noarch
PackageDescription	virtualenv is a tool to create isolated Python 2 environments. virtualenv is a successor to workingenv, and an extension of virtual-python. It is written by Ian Bicking, and sponsored by the Open Planning Project. It is licensed under an MIT-style permissive license.
PackageMaintainer	wally <wally>
PackageName	python2-virtualenv
PackageRelease	3.mga7
PackageVersion	16.1.0
SHA-1	80C3D6EEFF34E613894266E124D7048EECD12C57
SHA-256	347925C8873FE783673FD3695B21ABAF7A288223644D301D16A6C757434E9087

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	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