Parents (Total: 23)

The searched file hash is included in 23 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	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	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	60E7E993DD90F33D7103E6B7EF2E8294
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	pterjan <pterjan>
PackageName	python2-dogpile-cache
PackageRelease	1.mga7
PackageVersion	0.6.8
SHA-1	1ECBA2CB82059A2DC27F9CE9EDC77C5F98889E8D
SHA-256	796F729DD28FBC2DF7A020B9368835594661989959E8C561F61BB2AF9282A4B8

Key	Value
MD5	957D7543834638926FF7D741E394DE1E
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	lp151.10.1
PackageVersion	0.6.7
SHA-1	2900B5BCE5389F2DF0243D5901E79654F913BBA6
SHA-256	6040A631393660B7B8CEF47964E890F9203589910F506D514E2D74A1E81FA485

Key	Value
MD5	5600AA24C3D110C88BD93214B55233C8
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	10.1
PackageVersion	0.6.7
SHA-1	2DB7BD4898A0F84B5DC2E0E40CA26ECCE4025E5B
SHA-256	55E2EDD40D98A3EBEEAEF308320889157A13E1260B5F9874D1F7E541018EFFDC

Key	Value
MD5	7C72D313A5069226A8F423C83E076E22
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	1.el8.1
PackageVersion	0.6.8
SHA-1	34634E83B2BA877C077008A5DF85677E22A916CA
SHA-256	EA155B509983EB0CFF027E1E020F3C0944B1ABBA578F5C7A23F1AA0FAFFB0954

Key	Value
MD5	F06EB95E52C9AD00E3F7B7C7961FB3C8
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.1
PackageVersion	0.6.7
SHA-1	540C0A6F176D26906B217AFC618877687274577F
SHA-256	770E877FF9E956605E80757E1ED3012EBBDA47480D710DA3FE1CECC8E84577AD

Key	Value
MD5	AC67A9ECFE5E1AB0351A976830CC92CD
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	bp151.8.4
PackageVersion	0.6.7
SHA-1	5835124EBAFE332C379C1861CE1129F321392DD2
SHA-256	D60554CC298967A93B844569B451CF3218D36126611940B66248DAA005A02653