Key | Value |
---|---|
FileName | ./usr/share/doc/python-dogpile.cache-doc/html/_sources/api.rst.txt |
FileSize | 1357 |
MD5 | 9A4A848BF76CD5F49C46E10816D0EDB9 |
SHA-1 | 41922F400D75D83DC636AAE59722AB87251BD060 |
SHA-256 | FD6085C5992F3562475142E023D5DB66943A78BBDB9F4F4D986FE33B4F9218A6 |
SSDEEP | 24:fOVWYUAuG6ST9YSwpnOwO5ew+LrQVWg2bWX3XPt7c11g2/:fdYUzG6i9YfpOwO5N4rQ/gWX3X1411r/ |
TLSH | T14321381EF82D1C130AF608B1B6A295F5F56AA25FF19043346C2E46852984F1CBCE6F7C |
hashlookup:parent-total | 4 |
hashlookup:trust | 70 |
The searched file hash is included in 4 parent files which include package known and seen by metalookup. A sample is included below:
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 | 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 | 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 | 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 |