Key | Value |
---|---|
FileName | ./usr/lib/python2.7/site-packages/dogpile/lock.pyo |
FileSize | 5460 |
MD5 | 440887A0F1E03D503F06433CFB82E764 |
SHA-1 | 064703B14C1F6C5F8902AE0BBAF4F83B0AC88A6B |
SHA-256 | E4759BE808A9B7BA0943A6BAD24CB9FEED7C653708AAAC20B7DCA915FEA4385B |
SSDEEP | 96:BtqIj21CVfaByXB350Oq4lPmVZxBYq9bQfV3R+DkzDhm87:BgIihCB3hPmVZwObu3R+DQQw |
TLSH | T1DCB140D5FB98037BD12250B3A5B01296EBB4E17722066791322CD4797F4AB74C13F2E6 |
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 | 33793CC2F8394D12B5E12FACDB0190BD |
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 | python2-dogpile-cache |
PackageRelease | 10.12 |
PackageVersion | 0.6.7 |
SHA-1 | 013526239303502BC8F01E8EC9DA75621C0AFEA9 |
SHA-256 | 07FA48CE92B698EA452F2A0DCAA7893A74A1C6F2C422FB129583C9A7375F7246 |
Key | Value |
---|---|
MD5 | AC67A9ECFE5E1AB0351A976830CC92CD |
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 | python2-dogpile-cache |
PackageRelease | bp151.8.4 |
PackageVersion | 0.6.7 |
SHA-1 | 5835124EBAFE332C379C1861CE1129F321392DD2 |
SHA-256 | D60554CC298967A93B844569B451CF3218D36126611940B66248DAA005A02653 |
Key | Value |
---|---|
MD5 | 957D7543834638926FF7D741E394DE1E |
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 | python2-dogpile-cache |
PackageRelease | lp151.10.1 |
PackageVersion | 0.6.7 |
SHA-1 | 2900B5BCE5389F2DF0243D5901E79654F913BBA6 |
SHA-256 | 6040A631393660B7B8CEF47964E890F9203589910F506D514E2D74A1E81FA485 |
Key | Value |
---|---|
MD5 | 4602FBE966AABA45F90E630ED93C4238 |
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 | python2-dogpile-cache |
PackageRelease | lp152.10.1 |
PackageVersion | 0.6.7 |
SHA-1 | 7A2CF68E7E50765124B955416E2E44E59BD87886 |
SHA-256 | 2ABA27AF551C0790285AC50865968EC06F2019AAB3043FFF5FA6C20F19C680E2 |
Key | Value |
---|---|
MD5 | F06EB95E52C9AD00E3F7B7C7961FB3C8 |
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 | python2-dogpile-cache |
PackageRelease | 10.1 |
PackageVersion | 0.6.7 |
SHA-1 | 540C0A6F176D26906B217AFC618877687274577F |
SHA-256 | 770E877FF9E956605E80757E1ED3012EBBDA47480D710DA3FE1CECC8E84577AD |
Key | Value |
---|---|
MD5 | 9AE5181C4FC0522B5C07C7FAD7C637DC |
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 | python2-dogpile-cache |
PackageRelease | lp150.10.1 |
PackageVersion | 0.6.7 |
SHA-1 | F483B1ECE3595A99AD3D1C2CD6882DB812052DB3 |
SHA-256 | 5D06D0000660320BA5DB8EFC82887653F08A8D220BD8BB948BAABC2B37B7AB14 |
Key | Value |
---|---|
MD5 | E7B39AAFB07E3CCDBE43DB4EBE409296 |
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 | python2-dogpile-cache |
PackageRelease | bp150.10.2 |
PackageVersion | 0.6.7 |
SHA-1 | 81B9208A33B95F9E1990C46256974543B40DC5C6 |
SHA-256 | E4664E604D21D0425B397C0D615465D44304A3B07DFF7297465F7824B8C34DE1 |
Key | Value |
---|---|
MD5 | 8B3A963CF325E4F19AA358DFA2BF865D |
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 | python2-dogpile-cache |
PackageRelease | lp153.10.1 |
PackageVersion | 0.6.7 |
SHA-1 | A6C6099493A8033155D1FFC40027C3CDCD0010EE |
SHA-256 | EE9C3A73028DA1349776B09DAB2787FBD5798701A392953D10187A4186F837D2 |