Result for 874C290D80E4855829B8FF6A7199CF72260EDE1A

Query result

Key Value
FileName./usr/bin/virtualenv-3.6
FileSize400
MD5C7A3CDC9BCFCAB953CA4E62A1C726C56
SHA-1874C290D80E4855829B8FF6A7199CF72260EDE1A
SHA-25607DE93460B731ACA3703C3F4A61AA8594AC99E3A2B935ACF564B77954948ABE1
SSDEEP12:HsKu3aH1VZeRzoi9VrCF2aGNM1m2SfV5Utw:Pu3s8RzoAC0asTU+
TLSHT1D4E0681ED8B4CFB1F6E2019F7634627123060EA27E22602273E4B655FFC139A1C34A26
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
MD5ACB098BB25F2916F8B3AD7A27E0D3010
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.2.2
PackageVersion16.7.5
SHA-10F996A3CD5BA55F1E9125FEACFF6673EEB099A11
SHA-25645D35DFDCBB39BDB7823CF06A1AAEEB025CC853FB90975FF59363E1803D544AB