Key | Value |
---|---|
FileName | ./usr/lib/python3.4/site-packages/dogpile/cache/__pycache__/region.cpython-34.pyo |
FileSize | 48092 |
MD5 | 453C73A1EADA3F33E8AEB8E4972D26BD |
SHA-1 | 095D3A11F4F69775AA97D54C1D492E1C846C6D5F |
SHA-256 | 8CC987C66E2F70E79EDA72CFFD60AE3ACAE10E151D2908A872F4C866FF9DAA4A |
SSDEEP | 768:ZU4HDgZU/WrupF6/UgiVIOkoanDVBCAqga3h2lyHywCAcV5Z/i5zdSXI9ZWxwh5P:Jjge/WoF68gwkCAqgyklydCAcH1OpSXU |
TLSH | T17F23A4863B8513A7F8A6F5BA157DD1509770E01F370A6781F0ACC1A82F48B7996BB0DC |
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 | 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 | 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 |
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 |