Key | Value |
---|---|
FileName | ./usr/lib/python3.4/site-packages/dogpile/cache/__pycache__/proxy.cpython-34.pyo |
FileSize | 3372 |
MD5 | 199A9A413428F4DBB59E0E1A07C9EF7D |
SHA-1 | 684CB51BC5E6A450C9366ADA1ECA02B27A714CAD |
SHA-256 | 8BE422F5325B5BCBEE15C1904918DDA9021C9469A0C370AEBFDFC1AFF5BC3315 |
SSDEEP | 48:WNCuCrsqBlvdiINe3hXlbMK1bmpPcFtGGfcEGUZwz9jwpfmvJck7lTOOY:WAuGsqBroHfqpPcFbj6VwkvJck7lTOOY |
TLSH | T12B61DE568B036A5AFFB6E77E30B06260F53E806F460693213C9C75782FE42814DB4948 |
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 | 0C76DB1D1EEB48A3A69F2F9CEADA3F4E |
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.fc21 |
PackageVersion | 0.5.4 |
SHA-1 | A58E1B4706F16DF4EE24363BC5C0F306E1C23536 |
SHA-256 | 13B7F51663CF528F35040020C946A5988715AA4FB9EA281BD52D73015B533658 |
Key | Value |
---|---|
MD5 | 0812DC2D4555DC6CC98CCF4DBBD1E593 |
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.fc21 |
PackageVersion | 0.5.4 |
SHA-1 | 372E3D220DF59BFC0BEBE0361894FF2D2F48F883 |
SHA-256 | 54BCEE62664A4C35BBC1322B219E62A4150FBF9CE03DDC54FC0187F0BBC81199 |
Key | Value |
---|---|
MD5 | 93D1854FA3B9C7E956A60ADFEB54CEF5 |
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.fc21 |
PackageVersion | 0.5.4 |
SHA-1 | 71AF9E98217D17E4A2C9ADD957A20693C2CCAE58 |
SHA-256 | 1D3E30AD55877A53B094EA37935D53D4F387A881253737555A83698417A0BF5F |