Result for 6D7EB56E608C570DB682B8CD75801E35CDB4D781

Query result

Key Value
FileName./usr/lib/python3.4/site-packages/dogpile/cache/backends/__pycache__/memcached.cpython-34.pyo
FileSize12781
MD53B1E1F960CF70ED48AF28F9F92885630
SHA-16D7EB56E608C570DB682B8CD75801E35CDB4D781
SHA-256FF1BF99B7F33342B74374FA3BF8387150DAA15185C1A33D94233B1A75A1636C5
SSDEEP384:Fi2XLJ0oAuibxLRb/Bqlu8ynzidIdnqJ/AvB0G7wV+hFREX4+le5R6/6X:nbJSuGxLRb/Bqlu8ynzidIdnqJIpF7w0
TLSHT13F4273C96B4A48B6F562F7F9A171A230577AC50B27019B02F44CE17E1FCE6A8CD79094
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
MD50C76DB1D1EEB48A3A69F2F9CEADA3F4E
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
PackageNamepython3-dogpile-cache
PackageRelease1.fc21
PackageVersion0.5.4
SHA-1A58E1B4706F16DF4EE24363BC5C0F306E1C23536
SHA-25613B7F51663CF528F35040020C946A5988715AA4FB9EA281BD52D73015B533658
Key Value
MD50812DC2D4555DC6CC98CCF4DBBD1E593
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
PackageNamepython3-dogpile-cache
PackageRelease1.fc21
PackageVersion0.5.4
SHA-1372E3D220DF59BFC0BEBE0361894FF2D2F48F883
SHA-25654BCEE62664A4C35BBC1322B219E62A4150FBF9CE03DDC54FC0187F0BBC81199
Key Value
MD593D1854FA3B9C7E956A60ADFEB54CEF5
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
PackageNamepython3-dogpile-cache
PackageRelease1.fc21
PackageVersion0.5.4
SHA-171AF9E98217D17E4A2C9ADD957A20693C2CCAE58
SHA-2561D3E30AD55877A53B094EA37935D53D4F387A881253737555A83698417A0BF5F