Parents (Total: 8)

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	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
FileSize	19698
MD5	CC6C80E6B552563D61DA1C85DB515EF7
PackageDescription	Python virtual environment creator The virtualenv utility creates virtual Python instances, each invokable with its own Python executable. Each instance can have different sets of modules, installable via easy_install. Virtual Python instances can also be created without root access. . This is the command line script and manpage.
PackageMaintainer	Debian Python Modules Team <python-modules-team@lists.alioth.debian.org>
PackageName	virtualenv
PackageSection	python
PackageVersion	15.1.0+ds-1
SHA-1	D1CD5C370CEAADAA082986D79304AB45EF5A7DBF
SHA-256	ACF92D3B8F5CD4B5D8F43C12383B3DA8DA69D95CB87353F09581680C5BA82E55

Key	Value
FileSize	20076
MD5	04501F4A351386C7A5D980065C860F39
PackageDescription	Python virtual environment creator The virtualenv utility creates virtual Python instances, each invokable with its own Python executable. Each instance can have different sets of modules, installable via easy_install. Virtual Python instances can also be created without root access. . This is the command line script and manpage.
PackageMaintainer	Debian Python Modules Team <python-modules-team@lists.alioth.debian.org>
PackageName	virtualenv
PackageSection	python
PackageVersion	15.1.0+ds-2
SHA-1	78FD50A23BA79A728E51635D92C754E0C3B99D91
SHA-256	9B5DB954ECB2408A136F3D4CB073F577A787D0946EAE276E94A83C766FD5ACCB

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	712DEFA0AC82102EB7347F8585088444
PackageArch	noarch
PackageDescription	virtualenv 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
PackageMaintainer	Fedora Project
PackageName	python36-virtualenv
PackageRelease	5.el7
PackageVersion	15.1.0
SHA-1	509AD25F918B58EB0CE5F4173452E68CBCD32310
SHA-256	38FE8C6D1B3063EC1990D5CA30B8D394BF3AFC14CB8C295B16C42847892BB6C3

Key	Value
FileName	snap-hashlookup-import/bin/pkg/mod/github.com/gabriel-vasile/mimetype@v1.1.2/testdata/deb.deb
FileSize	4476
MD5	50698552FC4EA3C2C3DB31A36C6CADAA
PackageDescription	Python virtual environment creator The virtualenv utility creates virtual Python instances, each invokable with its own Python executable. Each instance can have different sets of modules, installable via easy_install. Virtual Python instances can also be created without root access. . This is the command line script and manpage.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	virtualenv
PackageSection	python
PackageVersion	15.1.0+ds-1.1
SHA-1	C1C4CD30C30F80069A085870B01381144C18243E
SHA-256	59EFE51AACA126EEAE1B8E028311F1D4EEFC9DCD194D5150C060F9CBC359E0E3
SHA-512	6AEB523C3C0D76BF7AEAF4002FE33FAB62A41433BCCBED42388A1A35ED08ABE373A932DC49DAAEAF327B9856280A6462A5609772485AB700278BAEC55572AE49
SSDEEP	96:z9iKH2+uLdDeCtHF76UAyyvNdnjAEIZEm9lUFN:z9i+vQDeCtlOfvNN6ZEm9ls
TLSH	T186919C2AA28095A1C11129A00BDF2950C31D3EA7FAEE1064B68DCEF603B75CD6BB40C2
insert-timestamp	1659227124.852648
mimetype	application/vnd.debian.binary-package
source	snap:mdTwaNga8m8NrBqqSH4FVIbtUwLWAhWj_15

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