Key | Value |
---|---|
FileName | ./usr/share/doc/python-dogpile.cache-doc/html/_sources/usage.rst.txt |
FileSize | 10477 |
MD5 | EFC8DA6E1B4C2209236EA3F58F8C0587 |
SHA-1 | 1C6099B2191D77FC7B72CCA55D685134281370B6 |
SHA-256 | 47413F709D5000FDAB655188451525FDD821CE76AF102325B894BD44CE54E6DE |
SSDEEP | 192:Ts7hmlLyH+DlBnT88p7vCbk+5/NwwUb4NbxAal2wDrc:A7hml8EvkQcNbSuc |
TLSH | T1C322934B6B8813F20DB6863E357DD1A09B38251F735A044478EFE25C2B11A6192BBDFC |
hashlookup:parent-total | 6 |
hashlookup:trust | 80 |
The searched file hash is included in 6 parent files which include package known and seen by metalookup. A sample is included below:
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 | 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 | 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 | 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 |