Result for 83985B9BE3F0F482069CF03DF7085D860D4BD978

Query result

Key Value
FileName./usr/lib/python3.6/site-packages/virtualenv_support/__pycache__/__init__.cpython-36.pyc
FileSize146
MD5E2EFBCC9FE139F3412EB6AB83AECDD52
SHA-183985B9BE3F0F482069CF03DF7085D860D4BD978
SHA-256B73752B8E41145BD2D4DC58DF9DE3CDA6DFD5B21A0E7FB954B10EA61EEE8B7B2
SSDEEP3:nKll+leh/wZWemWXP9YOKltVWrzxaLSVQK66BRkcTitn:nK/aeh/wV/9YlMrFxQsBD6
TLSHT182C09B48457553E3E53DFD377204271544CCDD6156DB95573D14524D5D0A3948C37401
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
MD570D83D2504B82B43E25F0F7BE410B295
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
PackageMaintainerFedora Project
PackageNamepython36-virtualenv
PackageRelease4.el7
PackageVersion15.1.0
SHA-1A2F2FE9B7FC54EF3172CBC2D28A905B20B9B9D37
SHA-256D457D9909E300E3F39A2EB3EAEDCEF443169235D01A8ED13513F6992567F87FA
Key Value
MD57C3D6D697B725FD6FFD9FFC80274FC70
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
PackageReleaselp151.1.2
PackageVersion15.1.0
SHA-17453F901E09CD059D053DBC2BB7BB7458D762017
SHA-256DA1C998A4F74CBE4D690ADABD7B3C31B5BF0131BDBFE82E0289A4B5966F46BA4
Key Value
MD551B1390E5C28EE5FBD57D3B134668408
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-1EC4787B0A5BD815CCAD3B6FD822420541A909420
SHA-2563584E5BBC2AA28B73F5884DCC29376D9EB1FE8D13679D89CC704E33176A64A0C
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