Result for 10AA661496EE031641A8BE5E5F6FF4652221F3D8

Query result

Key Value
FileName./usr/bin/virtualenv-2.7
FileSize400
MD520752CD13B3AF8E06BE43C0F886A3FFD
SHA-110AA661496EE031641A8BE5E5F6FF4652221F3D8
SHA-256FBE1A377BAFCDDCF81813D87D8BBCC3D839E3E72D653010CC691A4E4913CCFC3
SSDEEP12:HHKu3aH1VZeRzoi9VrCF2aGNM1m2SfV5Utw:Ku3s8RzoAC0asTU+
TLSHT142E0611ED474CF71F5E2019F7634617153060D927D22502173E47555FFC13991C34A26
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

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

Key Value
MD5A20ACA0CF3EEEFE128359D22BD13B1FD
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.2.2
PackageVersion16.7.5
SHA-1318E095082506419391EE586101D587F486CB05C
SHA-2564901401CC5714E3A04D0FD97E81FDAFD0FEA9E736E5B91C9BC40B449DE340F34