| Key | Value |
|---|---|
| FileName | ./usr/share/doc/packages/python3-virtualenv/README.rst |
| FileSize | 1135 |
| MD5 | CBF02532C88833D88636EC13A815B15D |
| SHA-1 | 7BC40F9124C6E6CBF88927D2D391FB9F439932B7 |
| SHA-256 | D30C1A1DA068A736A0E67E7F69C39030AAE02653E985634976C27C2DB0841EBD |
| SSDEEP | 24:5h40xiOI807fyAuSBDMr5isCiVNIVNPRlE1ASujXt:k0j07fFNDOCiVNIVNJe1A1 |
| TLSH | T1D22187FF59A06F26C390C1EFA2E15399D73B10FA9CCB4011A429BC708240BA594BC583 |
| hashlookup:parent-total | 8 |
| hashlookup:trust | 90 |
The searched file hash is included in 8 parent files which include package known and seen by metalookup. A sample is included below:
| Key | Value |
|---|---|
| MD5 | 2FDF39999F325173CA8CF513DE3E7C78 |
| PackageArch | noarch |
| PackageDescription | virtualenv 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). |
| PackageName | python2-virtualenv |
| PackageRelease | lp150.1.1 |
| PackageVersion | 15.1.0 |
| SHA-1 | B8090F92BFB7843F866F17D83B9E642D2BCE2B84 |
| SHA-256 | A7E6FF01665FE8C77B5C558DE1E659B6F7BEFFF5E3A35699D3729FFCB15E29ED |
| Key | Value |
|---|---|
| MD5 | 55865269597B0A09AB83C40557AE5882 |
| PackageArch | noarch |
| PackageDescription | virtualenv 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). |
| PackageName | python2-virtualenv |
| PackageRelease | lp151.1.2 |
| PackageVersion | 15.1.0 |
| SHA-1 | 2EC0ECED16196FB5C4355331ECAC497021AEFCBB |
| SHA-256 | 547AEC86DDA66EA29FA5B4F360A48E71D11B0A96455D5D77D7984394A70DA957 |
| Key | Value |
|---|---|
| MD5 | 7C3D6D697B725FD6FFD9FFC80274FC70 |
| PackageArch | noarch |
| PackageDescription | virtualenv 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). |
| PackageName | python3-virtualenv |
| PackageRelease | lp151.1.2 |
| PackageVersion | 15.1.0 |
| SHA-1 | 7453F901E09CD059D053DBC2BB7BB7458D762017 |
| SHA-256 | DA1C998A4F74CBE4D690ADABD7B3C31B5BF0131BDBFE82E0289A4B5966F46BA4 |
| Key | Value |
|---|---|
| MD5 | 51B1390E5C28EE5FBD57D3B134668408 |
| PackageArch | noarch |
| PackageDescription | virtualenv 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). |
| PackageName | python3-virtualenv |
| PackageRelease | lp150.1.1 |
| PackageVersion | 15.1.0 |
| SHA-1 | EC4787B0A5BD815CCAD3B6FD822420541A909420 |
| SHA-256 | 3584E5BBC2AA28B73F5884DCC29376D9EB1FE8D13679D89CC704E33176A64A0C |
| Key | Value |
|---|---|
| MD5 | 08E59FA30B6230B562B18EA0964EB751 |
| PackageArch | noarch |
| PackageDescription | virtualenv 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). |
| PackageName | python2-virtualenv |
| PackageRelease | lp150.1.1 |
| PackageVersion | 15.1.0 |
| SHA-1 | 96DCAFAA2C2F6D3DA24A4F364014EC7A40E2C6F8 |
| SHA-256 | E3174660888F111CEBA749AA19E5779268B91892F5B61D6C1B091ADB46337A24 |
| Key | Value |
|---|---|
| MD5 | 5362982EF3D64106FC1439A8F508D24A |
| PackageArch | noarch |
| PackageDescription | virtualenv 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). |
| PackageMaintainer | https://bugs.opensuse.org |
| PackageName | python2-virtualenv |
| PackageRelease | lp150.1.9 |
| PackageVersion | 15.1.0 |
| SHA-1 | 8679E812D5DD2ED45B4A31E1C3BE5DB8D39358F8 |
| SHA-256 | 5A16891BBDAE35999266CE60D2A448EF10D399EFF8BB04DBC1271105563CFFA6 |
| Key | Value |
|---|---|
| MD5 | C0F4B64F7DECE54136630430D6962C29 |
| PackageArch | noarch |
| PackageDescription | virtualenv 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). |
| PackageMaintainer | https://bugs.opensuse.org |
| PackageName | python3-virtualenv |
| PackageRelease | lp150.1.9 |
| PackageVersion | 15.1.0 |
| SHA-1 | 43834D6BFED3BC5016979B5C59FF5C79E7BE7A36 |
| SHA-256 | 5D3EF8B072D8FD6C61825C8561B6341513E829184D5B09738E427815DA349402 |
| Key | Value |
|---|---|
| MD5 | 6B274C32253BE58CD7F26A9B0D5288B5 |
| PackageArch | noarch |
| PackageDescription | virtualenv 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). |
| PackageName | python3-virtualenv |
| PackageRelease | lp150.1.1 |
| PackageVersion | 15.1.0 |
| SHA-1 | 9CB424B2F6A6C74E3E1EDAB7AC8F9BEB86824C59 |
| SHA-256 | AD5912484B38B4A3B18A25A5358D6CF32522A1102F6D3DC3EDB6301A049849E3 |