Parents (Total: 4)

The searched file hash is included in 4 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	9D18C3A52FE88D58D0D94B7C154EA4BC
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. 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	python39-virtualenv
PackageRelease	114.5
PackageVersion	20.10.0
SHA-1	6C4E2B7CEC80E0E0AAED7F66D5487D6469F91EAB
SHA-256	683C09D272B8CBD772E2D819886B7C543690F8B08B410CB2B8BFD78AD9AB5465

Key	Value
MD5	E878A90260B9E98354F64ED88AD15C11
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. 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	python39-virtualenv
PackageRelease	1.3
PackageVersion	20.10.0
SHA-1	2168D6D925124050DB074B85733DA1B3208EBC52
SHA-256	19B4EE1DA7CD8EF72D1FC10DED97E0D65EB4F44EAE212AFE9FDAF5EAB55BE367

Key	Value
MD5	36DDEB0EBBAD18783D7ADFF3554EC874
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. 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	python39-virtualenv
PackageRelease	114.4
PackageVersion	20.10.0
SHA-1	F445536A4AD58EC88425BBF7AEFDDB1B8F0800D5
SHA-256	2C2832FF7CFB4EFA4351577CE238E8F0BDF1C76F23CED395A03BBE4DEF4A30FD

Key	Value
MD5	F9AE7F7204C8373DA0509EE241040956
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. 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	python39-virtualenv
PackageRelease	114.4
PackageVersion	20.10.0
SHA-1	6552E20AE4E91272448BD6BA58923CAA66A40569
SHA-256	04F07D093BF912176AA9A414578D7EA9AD1AAB3915145EB9E0D8702715AF7E7A