Result for 05980ED575F2FE25F65607DB4C09854594C034EC

Query result

Key Value
FileName./usr/lib/python2.6/site-packages/dogpile/cache/backends/memcached.pyo
FileSize14361
MD52C0BF15CF9B70E9378B43CD12CBFA88D
SHA-105980ED575F2FE25F65607DB4C09854594C034EC
SHA-256CC99230B269CB9341F9EA2EF07A0921F8DCFBCA680FC2B40FCC5A4F44F71DC06
SSDEEP192:/7AdGwQdubljb3hvHdC2adagM2tMZUKi73bjW+G4DWKcEhU:0dGwQ4bxLoICKi7ZW90U
TLSHT15952308DF3580A77DA27457B32F00235D669F56B33036911B12C683A2F8869EC43EBD5
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
MD54C8822C27DF58FB93EA71560ACCD8EAA
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
PackageRelease1.el6
PackageVersion0.5.5
SHA-16DDFC1E538C75C1F36DDD9325A13F3293DFC9BAC
SHA-256414B8288D53FCC6B843425A0048CD2330E5002A5AD146A4331283170C484F3CB