Key | Value |
---|---|
FileName | ./usr/lib/python3.6/site-packages/dogpile/cache/__pycache__/util.cpython-36.opt-1.pyc |
FileSize | 4848 |
MD5 | BDE520465E6B03628712BF8A2DA6B301 |
SHA-1 | 0630175C5CDE532D79A5D4B3E0345F6EF77D238B |
SHA-256 | 147C1B4C88A27C1E6F2B1423111A6366BAC902F8ED2F0AF5FDF611485ABAC4E6 |
SSDEEP | 96:zhb1debyXUDaPkLE4AX4A64A5ZozbCCbUMXW5PSCgBrzfE5:NbiT4bLESU |
TLSH | T16DA1966D3982FB62FAA5F176426F81115135913F37C8C5A2313CC1CB6D06A4C2EA66EC |
hashlookup:parent-total | 8 |
hashlookup:trust | 90 |
The searched file hash is included in 8 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | 5600AA24C3D110C88BD93214B55233C8 |
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. |
PackageName | python3-dogpile-cache |
PackageRelease | 10.1 |
PackageVersion | 0.6.7 |
SHA-1 | 2DB7BD4898A0F84B5DC2E0E40CA26ECCE4025E5B |
SHA-256 | 55E2EDD40D98A3EBEEAEF308320889157A13E1260B5F9874D1F7E541018EFFDC |
Key | Value |
---|---|
MD5 | 0B9C53893ECBF353F7B851F39339F4B8 |
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. |
PackageName | python3-dogpile-cache |
PackageRelease | bp151.8.4 |
PackageVersion | 0.6.7 |
SHA-1 | F4FD0CFE197FD086C326FDA3EC214785AECFA6A3 |
SHA-256 | AA394A763E64B7F4FB1E4F5E36DFB52C74CB7E4679616B1FDD84AE0A525B4C89 |
Key | Value |
---|---|
MD5 | 3DB5EF32AB14C3D8FBC8E62EF930707D |
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. |
PackageName | python3-dogpile-cache |
PackageRelease | 10.12 |
PackageVersion | 0.6.7 |
SHA-1 | F71F28E301E8172E13869C7BB07785FCE3CEDA79 |
SHA-256 | A3ED5C9A2CC7FA112D0BE03F56A19C41CBA7F4BC0A2521276BCB31FCBC76EB78 |
Key | Value |
---|---|
MD5 | 7FC7B1E2DA0038FDAA688C0CBDDB7DDC |
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. |
PackageName | python3-dogpile-cache |
PackageRelease | lp151.10.1 |
PackageVersion | 0.6.7 |
SHA-1 | E266380DDBFE573FCE4847442791A12D5721BF61 |
SHA-256 | 45D7C7DC52B9B4699E5879E3286D98804A130591BA0EA082A9E609E0054D7A3A |
Key | Value |
---|---|
MD5 | 5365F090B3D3A28C83880A2DB68961B2 |
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. |
PackageName | python3-dogpile-cache |
PackageRelease | lp150.10.1 |
PackageVersion | 0.6.7 |
SHA-1 | E8C4FC46219F6086ACD9138720EC57042F59B0BB |
SHA-256 | D6DD36575B427BCFD7BB72BCC8480C756391BD563F3363B9B20DC1A5B89724FB |
Key | Value |
---|---|
MD5 | 9F5579702450CF79E36299880A1974BE |
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. |
PackageName | python3-dogpile-cache |
PackageRelease | lp153.10.1 |
PackageVersion | 0.6.7 |
SHA-1 | 11E11D7C069BBAD76EF20F03BD7A63ACB68C00CE |
SHA-256 | 801F2ED3A9ADC9F03E9325C96B08660DE37C8AA08CCEE4E81A9861D14BBB63FA |
Key | Value |
---|---|
MD5 | ED4555D19A94B594856D8201C045D5DD |
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. |
PackageName | python3-dogpile-cache |
PackageRelease | lp152.10.1 |
PackageVersion | 0.6.7 |
SHA-1 | C31EEE6DCE73AB52A5BCA8764724C6FF81B5ECE0 |
SHA-256 | ED29F488D4BF8A368FE922A3346B9825D96CAB259821F8D7EDE1ABF3655C3031 |
Key | Value |
---|---|
MD5 | 55D7B23BDCAF5DE6F0CB9469B0D0142C |
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. |
PackageName | python3-dogpile-cache |
PackageRelease | bp150.10.2 |
PackageVersion | 0.6.7 |
SHA-1 | 073B2D76BC6397F004D0E62639002E3DA6794B48 |
SHA-256 | A4E4B3448A782718DDA499189E436A8D58889D2D480A74592D6E28C5D090370D |