Parents (Total: 61)

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

Key	Value
MD5	C0E5ADC8E4612E52776D1A97A406A952
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	Fedora Project
PackageName	python2-virtualenv
PackageRelease	1.fc24
PackageVersion	14.0.6
SHA-1	01F046AA1AD96B51FE06A87260510A3CD9886285
SHA-256	7109806DD91201F56001B94911861FE979EAB55527073863772AE8AD3061BB05

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

Key	Value
MD5	1047C7F61F2E90986D3D1CFEA7B69297
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 BuildSystem <http://bugs.centos.org>
PackageName	python-virtualenv
PackageRelease	4.el7_7
PackageVersion	15.1.0
SHA-1	118309FE6AAC4FF2800E22A9911FC139DCF0A83F
SHA-256	F72D233FCECA106D5E3F01EB3AD222CA7B719AC94FFA739C7D5DAD81F1387C85

Key	Value
FileName	https://gbdi-packages.jsonar.com/rhel7.x_IBM_Guardium_big_data_security_installer_4.5.a.tar.gz
MD5	DBCEB0AEF732E9D31C5FFB2E8420429E
SHA-1	15679AD0960CA9070884097FE9BA2ECC38783A3B
SHA-256	925C1C1255FFFBFD89E12652B8EB16DC34A0D2D3A4D4387D0FB9578E843D709C
SSDEEP	50331648:lId4+316bTds+Nw09TDqqheBqLnXqNVkHLm2rUbsrc8WbGibv5VPBaxbeY44c:lIdD316/WBcbheBqLnXKSHHU+cdGijPz
TLSH	T1084A8899F4B0A5CFA426F53A5B90FFF252B0507296F6CC32E329034B51C77D03AA6859

Key	Value
MD5	5AE7BC3DDE7BBE277C695A496789253B
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	CBS <cbs@centos.org>
PackageName	rh-python36-python-virtualenv
PackageRelease	3.el7
PackageVersion	15.1.0
SHA-1	21ABF99CC73EBD2BA486623BBC837D361DA6BD5D
SHA-256	F88575C0EFC39504E3F424BDC3EF2A5DBDF0C3B60ECE618BBF549BB5CE966AA9

Key	Value
FileName	https://gbdi-packages.jsonar.com/rhel7.x_IBM_Guardium_big_data_security_installer_4.2.b.tar.gz
MD5	8C158A0034356CE840FD960D8064E639
SHA-1	2631B42E52C9B356B42A4D475A66C43EBB62B2F3
SHA-256	B78F2EE8A8A950FFDB1A7F1E2B02741F3B0DEAB479824539F88D53F545899202
SSDEEP	50331648:dgAEl0ZfmUQnFtfBlExcMPmU2GuIrz4jEB6Urllw7wRfd0jP6bqSIM6:2rlmKFSxZJTu2zsw6ozwMVdqP6bqSIM6
TLSH	T1F80A33C6F8736BBAD823703951B21FD795A6413982D6CC3BFB110B6607DB3C21A9A41D

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