Parents (Total: 11)

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

Key	Value
MD5	2FDF39999F325173CA8CF513DE3E7C78
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.1.1
PackageVersion	15.1.0
SHA-1	B8090F92BFB7843F866F17D83B9E642D2BCE2B84
SHA-256	A7E6FF01665FE8C77B5C558DE1E659B6F7BEFFF5E3A35699D3729FFCB15E29ED

Key	Value
MD5	C6AC895739530A03C32D60AB1C3756D7
PackageArch	noarch
PackageDescription	virtualenv is a tool to create isolated Python 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	CentOS Buildsys <bugs@centos.org>
PackageName	python2-virtualenv
PackageRelease	20.module_el8.5.0+763+a555e7f1
PackageVersion	15.1.0
SHA-1	C88EA677D68456F2429509487C309BD7BC6A28C3
SHA-256	714E4198E7D76CF2173A33E9A40A97768ABDFC10D000748BE40967F78AA0A7DB

Key	Value
MD5	55865269597B0A09AB83C40557AE5882
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	lp151.1.2
PackageVersion	15.1.0
SHA-1	2EC0ECED16196FB5C4355331ECAC497021AEFCBB
SHA-256	547AEC86DDA66EA29FA5B4F360A48E71D11B0A96455D5D77D7984394A70DA957

Key	Value
MD5	814E35B478C564739075D612F8921E7F
PackageArch	noarch
PackageDescription	virtualenv is a tool to create isolated Python 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	AlmaLinux Packaging Team <packager@almalinux.org>
PackageName	python2-virtualenv
PackageRelease	21.module_el8.5.0+2579+77770ab7
PackageVersion	15.1.0
SHA-1	EB32A505BF378F6F4694537CE1021FE8D8D12274
SHA-256	B62B7B8846544988A5E7F2901328A440CDA5FF05CB4CD2A3F2C64E2C7FB6923D

Key	Value
MD5	08E59FA30B6230B562B18EA0964EB751
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.1.1
PackageVersion	15.1.0
SHA-1	96DCAFAA2C2F6D3DA24A4F364014EC7A40E2C6F8
SHA-256	E3174660888F111CEBA749AA19E5779268B91892F5B61D6C1B091ADB46337A24

Key	Value
MD5	DD57441D96E2B597D8D98D5B3001E3AE
PackageArch	noarch
PackageDescription	virtualenv is a tool to create isolated Python 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	CentOS Buildsys <bugs@centos.org>
PackageName	python2-virtualenv
PackageRelease	21.module_el8.5.0+894+1c54b371
PackageVersion	15.1.0
SHA-1	C9E745EB0F29C70101C8052255FF7EC849E75BBB
SHA-256	C4C5C6D4F679A9E813E9C8A763AB917A0A14F50ACBFD5345E7F35FADE1DF6824

Key	Value
MD5	0B75DDE86DF6A80E4828D7EECEF11FBA
PackageArch	noarch
PackageDescription	virtualenv is a tool to create isolated Python 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	CentOS Buildsys <bugs@centos.org>
PackageName	python2-virtualenv
PackageRelease	20.module_el8.5.0+743+cd2f5d28
PackageVersion	15.1.0
SHA-1	F92D95DD36E6AAE5DB0E703DB23ADC9713597FED
SHA-256	FE5A43AD13EA34CC0D1581C3EC813D9CFCBB691315281A5119DEF2C5A9FB0619

Key	Value
MD5	B8803618AB6A11BD5725463B1C32E218
PackageArch	noarch
PackageDescription	virtualenv is a tool to create isolated Python 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	CentOS Buildsys <bugs@centos.org>
PackageName	python2-virtualenv
PackageRelease	19.module_el8.4.0+642+1dc4fb01
PackageVersion	15.1.0
SHA-1	A9743D4AEC58ED1D67E6799C79AFF8FD6A0CE34A
SHA-256	725DD6CEF78126F1CDE6264E5E9D11F869BFF8501B6932BB70B88DC5CE8AB467

Key	Value
MD5	5362982EF3D64106FC1439A8F508D24A
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	lp150.1.9
PackageVersion	15.1.0
SHA-1	8679E812D5DD2ED45B4A31E1C3BE5DB8D39358F8
SHA-256	5A16891BBDAE35999266CE60D2A448EF10D399EFF8BB04DBC1271105563CFFA6

Key	Value
MD5	70BE814C039B48D01B84B1A07BC069B8
PackageArch	noarch
PackageDescription	virtualenv is a tool to create isolated Python 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	CentOS Buildsys <bugs@centos.org>
PackageName	python2-virtualenv
PackageRelease	21.module_el8.6.0+940+9e7326fe
PackageVersion	15.1.0
SHA-1	CA2120DB1F01A021EBA1A52EC04B3975B6873350
SHA-256	59081505C8B34E570CA55BB5D7C5C20DFFE7FFB53A65352E5FA8B964A67E927B

Key	Value
MD5	28CBF479567987F460FE2E11F4DCB5F3
PackageArch	noarch
PackageDescription	virtualenv is a tool to create isolated Python 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	AlmaLinux Packaging Team <packager@almalinux.org>
PackageName	python2-virtualenv
PackageRelease	19.module_el8.3.0+2005+eb4bba01
PackageVersion	15.1.0
SHA-1	58A7E9D6AC275CF42CAC602DD1FE09ABC65F7440
SHA-256	6611AD02A64A28300143278F6062503409EEE83E4DC305626166B5AC585B7381