| Key | Value |
|---|---|
| FileName | ./usr/lib/python3.3/site-packages/dogpile/cache/__pycache__/util.cpython-33.pyc |
| FileSize | 8728 |
| MD5 | C65A7CCDD43A02571A473E136C90A9D5 |
| SHA-1 | 3303B84A61304CC5C3B8A91A61B6426F040D183A |
| SHA-256 | 87495F0432F235454F5419860D4282D6417B80AC9A9232129B24A6B05EE43E47 |
| SSDEEP | 192:4E9xiG2jjdhY6bzG1DEkJrsTvz4ju67DpjDBzCtj:JLe9kJgbzmu6fpDNCR |
| TLSH | T14D0254C0E7BD9ADBD6E54A7210310224C973F17366067B023360E4BA6DC97B7496FD51 |
| 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 | C49AF38E5E00FFFFB071649BBD0FA480 |
| 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 | 2.fc19 |
| PackageVersion | 0.4.2 |
| SHA-1 | F2E718AB2CEE49FDAC65D4598F3CF77A1AC2FE18 |
| SHA-256 | 7E166C3E0EC6EAD2635C75212CD46C0395738207550A2813791DAB90F876C506 |
| Key | Value |
|---|---|
| MD5 | A9F5A21B7D9CA94ECB65000708828046 |
| 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 | 2.fc19 |
| PackageVersion | 0.4.2 |
| SHA-1 | 819AB74B6BF456A25242C9FCB003F9222B02FF31 |
| SHA-256 | 2750E769AF2FCC6E91FADFE4F2858170269B0CE309652EE70BFA8CE67B77F2F9 |
| Key | Value |
|---|---|
| MD5 | A89376753636BC688F3116879DF51C8C |
| 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 | 2.fc19 |
| PackageVersion | 0.4.2 |
| SHA-1 | B7ED1ADEAE3AFA2B4195105893E31896A960D398 |
| SHA-256 | 9C5C88554B9D5B5B5DB280F901B56FDDFD32980E886836528B2127929C1645B4 |