Key | Value |
---|---|
FileName | ./usr/share/doc/python-dogpile.cache-doc/html/core_usage.html |
FileSize | 28240 |
MD5 | 0C1E34CFF931F0C20F48ECC72998362D |
SHA-1 | 2BE77D111A1114A7E8C8A42DF3B21F25AE68B9D3 |
SHA-256 | 42FA2E9056070F324727AE3C43A3B164B135F30A88CA8CF22C644D9168E53F5E |
SSDEEP | 384:AVnNFSpdJvtjKBWo5Eq2KJEwRckNp7nxe:O8jjKDpU6ckNhE |
TLSH | T1FFC299E6A6FA8A33417381D396EE1B75B4EA002EE4960140B6FD837847ECD507507DBE |
hashlookup:parent-total | 1 |
hashlookup:trust | 55 |
The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:
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 |