Result for 0A795CB35CADFF52E9713BEB15CF298652C6DFE6

Query result

Key Value
FileName./usr/lib/python2.7/site-packages/dogpile/cache/backends/memory.pyo
FileSize2173
MD5D2EBA4061E7CDDC80EF0C208A2B499ED
SHA-10A795CB35CADFF52E9713BEB15CF298652C6DFE6
SHA-256F37641BCD03E271DB359807945B1C1958007D53311449ADE1356889969D39052
SSDEEP48:0gHqOLz8duHBtfJ7aaWUzFPYWJMDZMMDSGPMDhCv9MD8MDZ9MDu:BHqI88htFafUzmLeJCK
TLSHT19B410E55D7AE8C87DBB6887A30B01126D178E2776303AA41361C31761F9C39A453E79A
hashlookup:parent-total3
hashlookup:trust65

Network graph view

Parents (Total: 3)

The searched file hash is included in 3 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD546F51DAD3B1C63292C99CFDAE8BB540E
PackageArchnoarch
PackageDescriptionA 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 <http://pypi.python.org/pypi/dogpile.core>`_ locking system, 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 <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.
PackageMaintainerFedora Project
PackageNamepython-dogpile-cache
PackageRelease2.fc19
PackageVersion0.4.2
SHA-199CB90CE3A0420DF8050E9B6E1485936FCA1D7C9
SHA-2567DAE84A674D2F14FF14BC7402C25B86E8A006AAB07CAADD461709DFA8328CCC4
Key Value
MD5104BE1C645FF4B80E7F8EF21AC468EA5
PackageArchnoarch
PackageDescriptionA 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 <http://pypi.python.org/pypi/dogpile.core>`_ locking system, 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 <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.
PackageMaintainerFedora Project
PackageNamepython-dogpile-cache
PackageRelease2.fc19
PackageVersion0.4.2
SHA-1A7109CC3CEC34C5AF460A97FE7E69C86236D348B
SHA-256624FEA0B05D2B8ED2B0EC6D70AFE4385AB634BFED35933FA104E9E80C4D34B9D
Key Value
MD5B8DB685605C0240220C522D4600E18EA
PackageArchnoarch
PackageDescriptionA 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 <http://pypi.python.org/pypi/dogpile.core>`_ locking system, 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 <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.
PackageMaintainerFedora Project
PackageNamepython-dogpile-cache
PackageRelease2.fc19
PackageVersion0.4.2
SHA-101F6EE2DE96F561EDAB9DCA570712984F2624182
SHA-256A9B4C1BF247C88DC057FA12CEA74D4A5B8E9E52EC840E805977A77CB49728A03