Key | Value |
---|---|
FileName | ./usr/lib/python2.7/site-packages/dogpile/cache/backends/__init__.pyo |
FileSize | 928 |
MD5 | 9CE82FCE28F091B7ABCAF8D1491EDDCF |
SHA-1 | 2F45F5B7018FED1255273DAE9745AB160B29C406 |
SHA-256 | FF09EEE106F2C97FEB5D09EE3163BDA12DE4C2418D0A2F701BBE48D20B382C8C |
SSDEEP | 24:lrkNs56D2aIqqsDQJuPBk9GCA4FXcg0wQuUaazUg:YdWrJuPBk9J32eGt |
TLSH | T16E11E5AF47AD4822DBB009B630F1027BDD4E701BFB849F01B516A09A19D6985425CABD |
hashlookup:parent-total | 4 |
hashlookup:trust | 70 |
The searched file hash is included in 4 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | 918F3E0BECFB7FA239D97D5957F4347D |
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 | python-dogpile-cache |
PackageRelease | 3.fc24 |
PackageVersion | 0.5.7 |
SHA-1 | 32A1EFCCBD2605412F4FDB7078B7A8DDF9E56E40 |
SHA-256 | 3837BCBA54722102B43B190E7E101B29A06F9D146B405D86C60C8DFF2FD110DA |
Key | Value |
---|---|
MD5 | D8D66E6AB33392BDFB1068F3FF980D22 |
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 | python-dogpile-cache |
PackageRelease | 3.fc24 |
PackageVersion | 0.5.7 |
SHA-1 | 2E965CFCB610C81999147D27F454641BF6739219 |
SHA-256 | 8EF9ACB1FBFE29E413B8120E60ECF42FE1964AAB59E7F3805C1293D974C67DED |
Key | Value |
---|---|
MD5 | 272D24835FB6A947978DD830867601AB |
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 | CBS <cbs@centos.org> |
PackageName | python-dogpile-cache |
PackageRelease | 1.el7 |
PackageVersion | 0.5.7 |
SHA-1 | 4D7235DD49CC7D48F5DEA98F1E3327E1C9874896 |
SHA-256 | 5B699A9527BD0F6E463B69867CC783C24A94C07C599C087D45DBB7FE697D1EFD |
Key | Value |
---|---|
MD5 | F21344B14C09C0089637BEA7B8A9DC2D |
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 | python-dogpile-cache |
PackageRelease | 1.el7 |
PackageVersion | 0.5.7 |
SHA-1 | CAAB61275E353E5EF046F2DC3155BC3D7213DDB3 |
SHA-256 | B778FA6D2B2FBF86684AEC4E5CD2B6DBDE51748FADD8BF782F8E7A14EE7A98E3 |