Result for 0916E1F3B264CAE43DA2EFB5E36D314533D8E32C

Query result

Key Value
FileName./usr/lib/python2.7/site-packages/virtualenv/seed/wheels/util.pyo
FileSize7116
MD57756095E69E4E033D08172F9B699407A
SHA-10916E1F3B264CAE43DA2EFB5E36D314533D8E32C
SHA-2568EACB9CE81F4777B376BF2120DECCFEDFE8A5F950D8B2A48091FBA51EF75FAB9
SSDEEP192:vGGtKHgI9m4KGdzfacaQhstx6m3YIb9OswAvobMSv2dZQXsIUTY0OP2+uY:vGGtKHDm4KGdziNVf6m3YIb9twAvIMSb
TLSHT1C3E1CE94B3A849E7D2711A79A1B0171B9664F0B37306BB927274B1795CC83EEC83F6C4
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
MD5272B97914C421118B6759A88AD7933B6
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. 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
PackageReleaselp151.102.1
PackageVersion20.2.2
SHA-1BC912824FD80290322D9193B74459C0C6A561F42
SHA-25615659F39528C1D70F800D49D4BB99CB2AC74459840445729ACBF88F7D1E04490