Parents (Total: 21)

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

Key	Value
MD5	B8DB685605C0240220C522D4600E18EA
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.fc19
PackageVersion	0.4.2
SHA-1	01F6EE2DE96F561EDAB9DCA570712984F2624182
SHA-256	A9B4C1BF247C88DC057FA12CEA74D4A5B8E9E52EC840E805977A77CB49728A03

Key	Value
MD5	D761034134469AC39C4FB49A0D903D17
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	python3-dogpile-cache
PackageRelease	1.fc20
PackageVersion	0.5.0
SHA-1	0357C6DCAA154DA5DA8C7CE338F66EDAA9C6D91F
SHA-256	E5446AC8B8382535A613287590C8DFBCFB198E8087E1B0BB52EED0C2ED1D07EA

Key	Value
MD5	D7EB165256C3070F8263261657849189
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.fc21
PackageVersion	0.5.4
SHA-1	0929FEFF7318D69804063339C585D9DC0994A320
SHA-256	67EA69DA438C90C7ADDF56B664B8D0C2D6D2A525AF47E7BE54F4FF6E878739B7

Key	Value
MD5	0812DC2D4555DC6CC98CCF4DBBD1E593
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	python3-dogpile-cache
PackageRelease	1.fc21
PackageVersion	0.5.4
SHA-1	372E3D220DF59BFC0BEBE0361894FF2D2F48F883
SHA-256	54BCEE62664A4C35BBC1322B219E62A4150FBF9CE03DDC54FC0187F0BBC81199

Key	Value
FileSize	28530
MD5	6A2611251E28EFD264C8BCFE17054CB4
PackageDescription	caching API built around the concept of a "dogpile lock" A cache API built around the concep of a "dogpile lock", which allows continued access to an expiring data value with a single thread generates a new value.
PackageMaintainer	Chuck Short <zulcss@ubuntu.com>
PackageName	python-dogpile.cache
PackageSection	python
PackageVersion	0.5.0-0ubuntu2
SHA-1	3A147A6A42C62813C810181E63EEBBFB680E1B91
SHA-256	C4D7001661EF36503A412662BCCA0C915377AE8996D3AA2C96A1DB3E909713C5

Key	Value
MD5	D01AA0B9EBBD7FBCE20DDB5EC91DFE9E
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.fc20
PackageVersion	0.5.0
SHA-1	3ECF8A79C56D411F720DB321449B1AE2D2C98C6E
SHA-256	D60E8A5888F0EB498D7AD351D04B81600104A03EE85C684294A91D3E51ECE7CE

Key	Value
MD5	272D24835FB6A947978DD830867601AB
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.5.7
SHA-1	4D7235DD49CC7D48F5DEA98F1E3327E1C9874896
SHA-256	5B699A9527BD0F6E463B69867CC783C24A94C07C599C087D45DBB7FE697D1EFD

Key	Value
MD5	4C8822C27DF58FB93EA71560ACCD8EAA
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.el6
PackageVersion	0.5.5
SHA-1	6DDFC1E538C75C1F36DDD9325A13F3293DFC9BAC
SHA-256	414B8288D53FCC6B843425A0048CD2330E5002A5AD146A4331283170C484F3CB

Key	Value
MD5	93D1854FA3B9C7E956A60ADFEB54CEF5
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	python3-dogpile-cache
PackageRelease	1.fc21
PackageVersion	0.5.4
SHA-1	71AF9E98217D17E4A2C9ADD957A20693C2CCAE58
SHA-256	1D3E30AD55877A53B094EA37935D53D4F387A881253737555A83698417A0BF5F

Key	Value
MD5	29CE9D5BA2FF38DF63161EF1C5C355EA
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	python3-dogpile-cache
PackageRelease	1.fc20
PackageVersion	0.5.0
SHA-1	7BFED51AC1E6A2AB9DDB2B0601825A3142931C90
SHA-256	D40D1CC5E40FFC74508A5FB36A029F9101BCD1635C35C4E602BA563ADCC9E46C