Result for 24C47AF813796D2D3E252647C4B3EEEF0384A7EA

Query result

Key Value
FileName./opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/virtualenv-15.1.0-py3.6.egg-info/PKG-INFO
FileSize3417
MD5E5DDD1EEE8E2B7631EBA8FE495EE37E3
SHA-124C47AF813796D2D3E252647C4B3EEEF0384A7EA
SHA-2563052D08A2BB8F285C2FFBA648F487551E810B4DB9356DDA4D0BE9E121D11A7D5
SSDEEP96:D05r2mKgLYlotj11dOlGQxbqOsn+S2y4jjaaDYr:qYmtjipqn+K
TLSHT19261538F1C8137B8D7C3D57A96584246C63180BF6E8E1C9C30BDA21C0F6277A467F12A
hashlookup:parent-total5
hashlookup:trust75

Network graph view

Parents (Total: 5)

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

Key Value
MD508E59FA30B6230B562B18EA0964EB751
PackageArchnoarch
PackageDescriptionvirtualenv 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).
PackageNamepython2-virtualenv
PackageReleaselp150.1.1
PackageVersion15.1.0
SHA-196DCAFAA2C2F6D3DA24A4F364014EC7A40E2C6F8
SHA-256E3174660888F111CEBA749AA19E5779268B91892F5B61D6C1B091ADB46337A24
Key Value
MD55362982EF3D64106FC1439A8F508D24A
PackageArchnoarch
PackageDescriptionvirtualenv 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).
PackageMaintainerhttps://bugs.opensuse.org
PackageNamepython2-virtualenv
PackageReleaselp150.1.9
PackageVersion15.1.0
SHA-18679E812D5DD2ED45B4A31E1C3BE5DB8D39358F8
SHA-2565A16891BBDAE35999266CE60D2A448EF10D399EFF8BB04DBC1271105563CFFA6
Key Value
MD55AE7BC3DDE7BBE277C695A496789253B
PackageArchnoarch
PackageDescriptionvirtualenv 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.
PackageMaintainerCBS <cbs@centos.org>
PackageNamerh-python36-python-virtualenv
PackageRelease3.el7
PackageVersion15.1.0
SHA-121ABF99CC73EBD2BA486623BBC837D361DA6BD5D
SHA-256F88575C0EFC39504E3F424BDC3EF2A5DBDF0C3B60ECE618BBF549BB5CE966AA9
Key Value
MD5C0F4B64F7DECE54136630430D6962C29
PackageArchnoarch
PackageDescriptionvirtualenv 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).
PackageMaintainerhttps://bugs.opensuse.org
PackageNamepython3-virtualenv
PackageReleaselp150.1.9
PackageVersion15.1.0
SHA-143834D6BFED3BC5016979B5C59FF5C79E7BE7A36
SHA-2565D3EF8B072D8FD6C61825C8561B6341513E829184D5B09738E427815DA349402
Key Value
MD56B274C32253BE58CD7F26A9B0D5288B5
PackageArchnoarch
PackageDescriptionvirtualenv 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).
PackageNamepython3-virtualenv
PackageReleaselp150.1.1
PackageVersion15.1.0
SHA-19CB424B2F6A6C74E3E1EDAB7AC8F9BEB86824C59
SHA-256AD5912484B38B4A3B18A25A5358D6CF32522A1102F6D3DC3EDB6301A049849E3