Key | Value |
---|---|
FileName | ./usr/lib/python3.4/site-packages/dogpile/cache/backends/__pycache__/redis.cpython-34.pyo |
FileSize | 6199 |
MD5 | B079114FB7F96992EA70E0E6D9477267 |
SHA-1 | 11299317941BAA7F1CB0AE9C72F7B7D7998FE6BA |
SHA-256 | E521129523816BC486F5A464102772E46C8AF38718A4963E33A8B02890779FB7 |
SSDEEP | 96:FWXdw5HdMRm1yq9qlXJn2mtOiktOM2Eqky4E/nMVlhDOYirkX/59cFb/iloL5Y:MXW59qm1yXlgr2EyPAhDOTIhm2OY |
TLSH | T118D16345AB03C81BFAF4F2B670B922189B71C25B37027302B4ECE8B81FCE7548975259 |
hashlookup:parent-total | 6 |
hashlookup:trust | 80 |
The searched file hash is included in 6 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | A8E196C21B19D604B38AE40D7DF59CC8 |
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 | 1.fc22 |
PackageVersion | 0.5.5 |
SHA-1 | 48F4338A2BC715403EE0DE46B16DD8D8458FFE7E |
SHA-256 | 09DE50B72787958B0D1AB07486830B2C86D6AE00CD344F546E8F3FE55E7E93DD |
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 | B0826A502E22921DAD9937377642DA0E |
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 | 1.fc22 |
PackageVersion | 0.5.5 |
SHA-1 | E1ADEFFA68597E98C6EADAC40E851F569E4C4398 |
SHA-256 | 036BD6504A752D9E66598A0D7281C1D7E6E196C84BD8510F7E0ADD952135A563 |
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 | 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 |
Key | Value |
---|---|
MD5 | 742BFFFB7096DB4E4F2A73322271D33E |
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 | 1.fc22 |
PackageVersion | 0.5.5 |
SHA-1 | 353B77E5BAA732864353A2D4EC005E8EF3B68CD0 |
SHA-256 | 6871506F99BD5ABDDD8130CCF032E52F5CFBB2ED66671331CF9FE11A3733C8E7 |