Key | Value |
---|---|
FileName | ./usr/lib/python3.4/site-packages/dogpile/cache/backends/__pycache__/memcached.cpython-34.pyo |
FileSize | 12841 |
MD5 | 933C1191FDEDF41B13D358B6072B508F |
SHA-1 | 20610219FAD16790ADFB434C418CC6726F9009BE |
SHA-256 | 0C63F6A493CF28642FEEED5DA2EB4A39B57809696BB8FB4F1DD5D0346239C829 |
SSDEEP | 384:CPzLQ0oABBbxLRRZzq0N1Ptd4ZK7YIAmz0GD7V5WFRv84YlejC6zQdU:EQSBhxLRRZzq0N1Ptd4ZK7YBUFD7V5Wj |
TLSH | T1744264C96B4A48B6F562F7F9A171A230577AC10B27015B02F44CE17E1FCE6A9CD79094 |
hashlookup:parent-total | 3 |
hashlookup:trust | 65 |
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 |
---|---|
MD5 | D617ADD9BF5CA31A1FA1F5C9578120EE |
PackageArch | noarch |
PackageDescription | 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 <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. |
PackageMaintainer | Fedora Project |
PackageName | python3-dogpile-cache |
PackageRelease | 2.fc23 |
PackageVersion | 0.5.5 |
SHA-1 | DE7878DFBD708D6BBBADA0F338982CC2FCB2F4E2 |
SHA-256 | B57A8B2F758F801F8F54D23842670B20C386EF7458DA89150206227DE2F240B7 |
Key | Value |
---|---|
MD5 | E9846DD3C3A18875085C09EBC251D8E8 |
PackageArch | noarch |
PackageDescription | 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 <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. |
PackageMaintainer | Fedora Project |
PackageName | python3-dogpile-cache |
PackageRelease | 2.fc23 |
PackageVersion | 0.5.5 |
SHA-1 | 8BD8B4B314A34577738269EAF674EC728C639398 |
SHA-256 | B11DF41D6C77E9BE04F72B7A7C41DC4EE56D97A5C4153484621732D8B00111BC |
Key | Value |
---|---|
MD5 | 08F89D390CA3A4D71B0BF81AD57CA40D |
PackageArch | noarch |
PackageDescription | 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 <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. |
PackageMaintainer | Fedora Project |
PackageName | python3-dogpile-cache |
PackageRelease | 2.fc23 |
PackageVersion | 0.5.5 |
SHA-1 | 54FD7EF971B56333DE7C7E5A9BBB3848D51A19DF |
SHA-256 | 5AF2F8305326CC020B408C5F8D9AD278DFEB7B5FD2987EE65804CA2E583EA508 |