Parents (Total: 94)

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

Key	Value
MD5	33793CC2F8394D12B5E12FACDB0190BD
PackageArch	noarch
PackageDescription	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 <http://pypi.python.org/pypi/dogpile.core>`_ locking system, 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 <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.
PackageName	python2-dogpile-cache
PackageRelease	10.12
PackageVersion	0.6.7
SHA-1	013526239303502BC8F01E8EC9DA75621C0AFEA9
SHA-256	07FA48CE92B698EA452F2A0DCAA7893A74A1C6F2C422FB129583C9A7375F7246

Key	Value
MD5	F1AEDACB6BAA8A492BC7539A7B14DFFE
PackageArch	noarch
PackageDescription	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 <http://pypi.python.org/pypi/dogpile.core>`_ locking system, 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 <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.
PackageMaintainer	Fedora Project
PackageName	python-dogpile-cache
PackageRelease	1.fc22
PackageVersion	0.5.5
SHA-1	062312AF26075DC8859E49CD84E0B10CBE287375
SHA-256	2D65EE0BD46FBF5A21FE7CFE1295DF8880A96D26AD7A3F1DBC7A13FEA0FE866A

Key	Value
MD5	55D7B23BDCAF5DE6F0CB9469B0D0142C
PackageArch	noarch
PackageDescription	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 <http://pypi.python.org/pypi/dogpile.core>`_ locking system, 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 <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.
PackageName	python3-dogpile-cache
PackageRelease	bp150.10.2
PackageVersion	0.6.7
SHA-1	073B2D76BC6397F004D0E62639002E3DA6794B48
SHA-256	A4E4B3448A782718DDA499189E436A8D58889D2D480A74592D6E28C5D090370D

Key	Value
MD5	A8341E4A0053459A2D5C5817B27B0F21
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.
PackageMaintainer	CBS <cbs@centos.org>
PackageName	python3-dogpile-cache
PackageRelease	1.el8
PackageVersion	0.9.0
SHA-1	07496BBE5A801C190EEE0740DFC2A253E8686088
SHA-256	6D487527AEEA6FA2316203549954990380BB9B17A90CEBC07599BF51397CC2D7

Key	Value
MD5	60DAD7BB15875E6BC7A4C889F6C1B1FC
PackageArch	noarch
PackageDescription	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 <http://pypi.python.org/pypi/dogpile.core>`_ locking system, 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 <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.
PackageMaintainer	CBS <cbs@centos.org>
PackageName	python-dogpile-cache
PackageRelease	1.el7
PackageVersion	0.6.2
SHA-1	0ACA7EEA1555566B546F410A742CF8DE32F2AF93
SHA-256	2E81C59A3B2A1F8AA8235CE1C3C4E6DE483500DC6939E2EB06859DB3A8F13EA0

Key	Value
MD5	DD60029915CF9D70BD32A0DB9D62A565
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.
PackageMaintainer	Fedora Project
PackageName	python3-dogpile-cache
PackageRelease	2.fc32
PackageVersion	0.9.0
SHA-1	0C8CD7B9B09880D9239C3EC5B3A312B64C7533D8
SHA-256	499B97BA9F2CF59C1D15F7955F97C9881CE2522BBD100F9634C8485B1C799C26

Key	Value
MD5	DDB083C4B36120D71576F16C6F76F55E
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.
PackageMaintainer	Fedora Project
PackageName	python2-dogpile-cache
PackageRelease	1.el8.1
PackageVersion	0.6.8
SHA-1	0F7652B9674CF2F2C593B40DAD17D7FB7C0623CB
SHA-256	5043A90EBE9CB7DFEDC7D354DC347A2845081C6BC9A81DD9ECAAB673CCAB9904

Key	Value
MD5	9F5579702450CF79E36299880A1974BE
PackageArch	noarch
PackageDescription	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 <http://pypi.python.org/pypi/dogpile.core>`_ locking system, 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 <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.
PackageName	python3-dogpile-cache
PackageRelease	lp153.10.1
PackageVersion	0.6.7
SHA-1	11E11D7C069BBAD76EF20F03BD7A63ACB68C00CE
SHA-256	801F2ED3A9ADC9F03E9325C96B08660DE37C8AA08CCEE4E81A9861D14BBB63FA

Key	Value
MD5	6CD3DFDD5BB685181E042674014DEE97
PackageArch	noarch
PackageDescription	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 <http://pypi.python.org/pypi/dogpile.core>`_ locking system, 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 <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.
PackageMaintainer	Fedora Project
PackageName	python-dogpile-cache
PackageRelease	2.fc23
PackageVersion	0.5.5
SHA-1	1C6E5B2B426153A82BB6C74F77B10EF812342BE2
SHA-256	89C279A77F60EA617053EE2A0FDF72C1852B9D6F38D8270FF34EE7F63C5D6F41

Key	Value
FileSize	35928
MD5	AC78DB82FF685D144D082CF8D7417315
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	0.9.0-0ubuntu1
SHA-1	1E271B0EDCF4DEDE894BD280E39A7F2C29C81119
SHA-256	78F012A4E8E3BF4C7EF49AFE936E0F84B44B06FD783511A9A486297BB432C4D3