Key | Value |
---|---|
FileName | ./usr/share/doc/python-dogpile.cache-doc/html/_sources/index.rst.txt |
FileSize | 1215 |
MD5 | C490B351A35AC2E6B5E9B4754C304001 |
SHA-1 | 063FD9530DC4BBB574F3FB7170BDA1F3F78ACE19 |
SHA-256 | E86CD725286294D8C71E92E8A9FD68495F95CB783FEF2D787BE2B14091627AC1 |
SSDEEP | 24:tGc1GoC4Uo8OLJQJolbKj0bKw15YIUMgALl3Q/3k10Cm2scS5K0:tL03KDJQ6lbKWKw1GhzALl3E3k1lm2ar |
TLSH | T176213336E71912B101E14595386740E0D3AF50AEBB125086D055C1B82686F3ED73BFF8 |
hashlookup:parent-total | 11 |
hashlookup:trust | 100 |
The searched file hash is included in 11 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
FileSize | 65904 |
MD5 | B75712F8563D023D3395675CA5B181CB |
PackageDescription | caching front-end based on the Dogpile lock - doc 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 documentation. |
PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
PackageName | python-dogpile.cache-doc |
PackageSection | doc |
PackageVersion | 0.9.0-0ubuntu1 |
SHA-1 | 013F2F9C97635FE62554186F2565C3F2DC6F7B40 |
SHA-256 | A41702EBBEAFD47271D4D7187673E25178851447A172D21DDDE1EF20BBC03D9B |
Key | Value |
---|---|
FileSize | 82412 |
MD5 | E0F005E2753DA5B31EA81E8C377B0A86 |
PackageDescription | caching front-end based on the Dogpile lock - doc 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 documentation. |
PackageMaintainer | PKG OpenStack <openstack-devel@lists.alioth.debian.org> |
PackageName | python-dogpile.cache-doc |
PackageSection | doc |
PackageVersion | 0.6.2-5 |
SHA-1 | 12D4D2DD5ED762F60FDEB05C5D828A3F9749C3BB |
SHA-256 | F27C33F9ECB47464A0B61C891A2489970B0B900804F78FF8D273ECC4664DCE6D |
Key | Value |
---|---|
FileSize | 66540 |
MD5 | 8D851C7ED488D8054227E34A4B6C0E34 |
PackageDescription | caching front-end based on the Dogpile lock - doc 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 documentation. |
PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
PackageName | python-dogpile.cache-doc |
PackageSection | doc |
PackageVersion | 1.0.1-0ubuntu1 |
SHA-1 | ADA77BCE81829132BA81EAA396799D2A986AA8AF |
SHA-256 | 3370CC43759CC072601A989ABDD9B00CC5C6FBD431EB014C4573803806A670D6 |
Key | Value |
---|---|
FileSize | 64812 |
MD5 | 08338A7958DECAC9033EEBF188E1719D |
PackageDescription | caching front-end based on the Dogpile lock - doc 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 documentation. |
PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
PackageName | python-dogpile.cache-doc |
PackageSection | doc |
PackageVersion | 0.6.2-6 |
SHA-1 | D93AA553675C42513D9F54F3B60FBB7D4361597B |
SHA-256 | A1036BE3F612B0BD3899DB6B76803C32C8B8E42F32BFFD0CB105CD4523D7B585 |
Key | Value |
---|---|
FileSize | 64172 |
MD5 | 224A525F15BDC243C186A3AEFC00E67F |
PackageDescription | caching front-end based on the Dogpile lock - doc 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 documentation. |
PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
PackageName | python-dogpile.cache-doc |
PackageSection | doc |
PackageVersion | 0.6.2-0ubuntu1 |
SHA-1 | 3069F1F016A424456E5548B740FDC748B106AB19 |
SHA-256 | 1E5215375A87A48C74EBFD53B3E6659555B1405629231C7266915B8AFD97CB81 |
Key | Value |
---|---|
FileSize | 68632 |
MD5 | 3E7367B1647EED64D9BA892BBC527CF5 |
PackageDescription | caching front-end based on the Dogpile lock - doc 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 documentation. |
PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
PackageName | python-dogpile.cache-doc |
PackageSection | doc |
PackageVersion | 0.7.1-1ubuntu1 |
SHA-1 | A8963AE039B142F1DF05150B3F15C8BB3D0A381C |
SHA-256 | 66AA9CD7FE2D35B28713C2262F53ACC14E6530866E4F814D72B04BBE84E4011E |
Key | Value |
---|---|
FileSize | 62068 |
MD5 | 332CEB04FB9C98F3F880B037B958621F |
PackageDescription | caching front-end based on the Dogpile lock - doc 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 documentation. |
PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
PackageName | python-dogpile.cache-doc |
PackageSection | doc |
PackageVersion | 0.6.2-5 |
SHA-1 | AFA986C995EC7529EA1C56F58E1203BEA7757850 |
SHA-256 | 2847AFB1D2EEA4302D15BB3563A3ECAE462A75DADCD5453218DC24C735C54A83 |
Key | Value |
---|---|
FileSize | 89976 |
MD5 | 28489731884A59C9C8BC4D9C8F937777 |
PackageDescription | caching front-end based on the Dogpile lock - doc 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 documentation. |
PackageMaintainer | Debian OpenStack <team+openstack@tracker.debian.org> |
PackageName | python-dogpile.cache-doc |
PackageSection | doc |
PackageVersion | 1.0.2-2 |
SHA-1 | 89ADB1C0C05617C504D808218D25509A68D7AD4C |
SHA-256 | 379BF1E98DCDFEABB82F56A31F2068CDA60FB48FD885FF71113902E207CCCC79 |
Key | Value |
---|---|
FileSize | 70712 |
MD5 | 9D92BE760CE8B051CD7559A298128FD3 |
PackageDescription | caching front-end based on the Dogpile lock - doc 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 documentation. |
PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
PackageName | python-dogpile.cache-doc |
PackageSection | doc |
PackageVersion | 1.1.2-1 |
SHA-1 | A715DBC8E7E79498B1C6A4BA834611283D65DCFE |
SHA-256 | 1C8B6F6309ADAF50E58DC90C2A2839B9F1E12CD0B3323D35D206F0B9E41E3A56 |
Key | Value |
---|---|
FileSize | 82588 |
MD5 | CA19EF5378AE3BD55CFDD95E98DE80FE |
PackageDescription | caching front-end based on the Dogpile lock - doc 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 documentation. |
PackageMaintainer | Debian OpenStack <team+openstack@tracker.debian.org> |
PackageName | python-dogpile.cache-doc |
PackageSection | doc |
PackageVersion | 0.6.2-6 |
SHA-1 | E57B3CB259ADD1862D0057C1492190D153A0858A |
SHA-256 | AD9813C9659E615B07055BD1FE1D67AC3397C90DF80AEB244E6E95FB4A85185B |
Key | Value |
---|---|
FileSize | 101264 |
MD5 | BB4E1D676C49A828BE52E692152389E0 |
PackageDescription | caching front-end based on the Dogpile lock - doc 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 documentation. |
PackageMaintainer | Debian OpenStack <team+openstack@tracker.debian.org> |
PackageName | python-dogpile.cache-doc |
PackageSection | doc |
PackageVersion | 1.1.4-2 |
SHA-1 | BEB35704215EBD27E5F2E6323578B1777B83AA2F |
SHA-256 | 145FFA1D636FD48FD90D2CD9DD8E3E253CA98BDDBBB723E35DA00782E2DF83CA |