Parents (Total: 3)

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

Key	Value
FileSize	36276
MD5	5B43C13A17CEDB973D586A71C0563B4F
PackageDescription	caching front-end based on the Dogpile lock - Python 3.x A caching API built around the concept of a "dogpile lock", which allows continued access to an expiring data value while a single thread generates a new value. . dogpile.cache builds on the dogpile.core locking system (see http://pypi.python.org/pypi/dogpile.core), which implements the idea of "allow one creator to write while others read" in the abstract. Overall, dogpile.cache is intended as a replacement to the Beaker (see http://beaker.groovie.org) caching system, the internals of which are written by the same author. All the ideas of Beaker which "work" are re-implemented in dogpile.cache in a more efficient and succinct manner, and all the cruft (Beaker's internals were first written in 2005) relegated to the trash heap. . This package provides the Python 3.x module.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	python3-dogpile.cache
PackageSection	python
PackageVersion	1.0.1-0ubuntu1
SHA-1	0C414A9C1188FB8C41C1A700B7AEC937320973B2
SHA-256	81B1F639585F71315A03BD57DE6303A89129938E1AB2C9A894CD97E9563F0B35

Key	Value
MD5	5FAAD25C374FA9B7C6CFC39D7C3B646D
PackageArch	noarch
PackageDescription	Dogpile consists of two subsystems, one building on top of the other. dogpile provides the concept of a "dogpile lock", a control structure which allows a single thread of execution to be selected as the "creator" of some resource, while allowing other threads of execution to refer to the previous version of this resource as the creation proceeds; if there is no previous version, then those threads block until the object is available. dogpile.cache is a caching API which provides a generic interface to caching backends of any variety, and additionally provides API hooks which integrate these cache backends with the locking mechanism of dogpile. Overall, dogpile.cache is intended as a replacement to the Beaker caching system, the internals of which are written by the same author. All the ideas of Beaker which "work" are re- implemented in dogpile.cache in a more efficient and succinct manner, and all the cruft (Beaker's internals were first written in 2005) relegated to the trash heap.
PackageName	python3-dogpile-cache
PackageRelease	13.39
PackageVersion	1.0.1
SHA-1	10BB33D943AF4B4A5A584D698AC0D34649EB02AA
SHA-256	5E1AECAB535DB1C3D8CCA641F0D21A12C55379A8A2DA4ABCDCF7D3E6DF00CBAB

Key	Value
MD5	0E729058FC5304C5A0E5B702BBFDCBF7
PackageArch	noarch
PackageDescription	Dogpile consists of two subsystems, one building on top of the other. dogpile provides the concept of a "dogpile lock", a control structure which allows a single thread of execution to be selected as the "creator" of some resource, while allowing other threads of execution to refer to the previous version of this resource as the creation proceeds; if there is no previous version, then those threads block until the object is available. dogpile.cache is a caching API which provides a generic interface to caching backends of any variety, and additionally provides API hooks which integrate these cache backends with the locking mechanism of dogpile. Overall, dogpile.cache is intended as a replacement to the Beaker caching system, the internals of which are written by the same author. All the ideas of Beaker which "work" are re- implemented in dogpile.cache in a more efficient and succinct manner, and all the cruft (Beaker's internals were first written in 2005) relegated to the trash heap.
PackageName	python3-dogpile-cache
PackageRelease	13.28
PackageVersion	1.0.1
SHA-1	6622422745BABD08ECF4FAEC2311265983D8C0C7
SHA-256	84D33C679541A0668E65C4F134A336FC04707D53925065644137BBFF3817249E