Result for 016FC4C748F42FC04AB9102DD50F81E5C53E4FDD

Query result

Key Value
FileName./usr/share/doc/python-dogpile.cache-doc/html/_static/up.png
FileSize345
MD510306042A1409FA344E110E7F13C5E9E
SHA-1016FC4C748F42FC04AB9102DD50F81E5C53E4FDD
SHA-256F7751936F3CA7FA74CD28786F7C14D4013C60B14AB16BF844BD2FA637DD701C7
SSDEEP6:6v/lhPfp8RFknMISg6sp739JO858SBf/HC+/2ZSTQrG6tsup:6v/7uKMy6spe8CYHf22QSQ
TLSHT172E0754AA030AFD9EC00C053330218E1F8A123CDC8A3C304C44CC027A42DE0D04E1F4B
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

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
FileSize82412
MD5E0F005E2753DA5B31EA81E8C377B0A86
PackageDescriptioncaching 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.
PackageMaintainerPKG OpenStack <openstack-devel@lists.alioth.debian.org>
PackageNamepython-dogpile.cache-doc
PackageSectiondoc
PackageVersion0.6.2-5
SHA-112D4D2DD5ED762F60FDEB05C5D828A3F9749C3BB
SHA-256F27C33F9ECB47464A0B61C891A2489970B0B900804F78FF8D273ECC4664DCE6D