Result for 0973A5359FCE451DD684BB806C3BC8E94A6B9228

Query result

Key Value
FileName./usr/lib/python3.8/site-packages/virtualenv/__pycache__/report.cpython-38.pyc
FileSize1420
MD5EE2A6CBF54A844E1EA7ADE4CF6545B31
SHA-10973A5359FCE451DD684BB806C3BC8E94A6B9228
SHA-25613F28522CBFC04A5E3581A71315A37EF6CAD6658B6805F5BB8FB4D0BF4AFD0A3
SSDEEP24:dUOUCXeCFNMyltIGFrdjk7WG8smP4jjrGI8WStAEwUOBwpKsMOBBQOPYllj2jVN:+OUiNMylJdk7WG8Mjd8WdEXOqYOBLwl4
TLSHT111218659C00B4E6EFA39F2B46116131DEEA09A924B52F0E77C09B31C0E099D64D78B4A
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
MD5B785313BFD135A4259EAF24626CA60D2
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).
PackageNamepython3-virtualenv
PackageRelease2.1
PackageVersion20.0.17
SHA-1D0799D2AC8C9CDED56056C00357D608BB52C5AB3
SHA-256C09B0643D462FF205F9003DDF62F55075A6AD51CBFDF017BA0B808D56C13BF98