| Key | Value |
|---|---|
| FileName | ./usr/lib/python2.7/site-packages/dogpile/cache/plugins/__init__.pyo |
| FileSize | 153 |
| MD5 | B4E58A44D5C6CEBE0D6D39C3CC939073 |
| SHA-1 | 098736CA160B3D5F60C415A2A4B4D65273C48EF6 |
| SHA-256 | B7418F1AB6DB9B3B9682ABDFE97CD917EF7AF4673BA5726D050F1096D0AD958C |
| SSDEEP | 3:l5zllOleh/Tj3tNltNltW/69Y3IMmoWrz0CGv5jXKoncRzaiitn:l5JlKeh/T4/69Y3xmDrCRXncRaF |
| TLSH | T149C09BD1F3398957D6365975B100163D41CCC573A113B9517624055E0C5D06A493F9C5 |
| 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 | D7EB165256C3070F8263261657849189 |
| 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.fc21 |
| PackageVersion | 0.5.4 |
| SHA-1 | 0929FEFF7318D69804063339C585D9DC0994A320 |
| SHA-256 | 67EA69DA438C90C7ADDF56B664B8D0C2D6D2A525AF47E7BE54F4FF6E878739B7 |
| Key | Value |
|---|---|
| MD5 | 74E8C2D1C33FB9D2F4CB134EC478A647 |
| 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.fc21 |
| PackageVersion | 0.5.4 |
| SHA-1 | E680525A1FDF2AEC1E3C9842E0CE631D63B1DFFE |
| SHA-256 | 0EA20F1BEAC88479832343E020303846837FC3BFA2B507DCCFA7FD43CB39F567 |
| Key | Value |
|---|---|
| MD5 | 3D91BE0AF74527524CECFECDC38874B1 |
| 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.fc21 |
| PackageVersion | 0.5.4 |
| SHA-1 | 7EA9C8E4AC6565BD7D2E9F86CA041B5E6B3E6AD6 |
| SHA-256 | A0F6EA40B25C7E0B0B147A4AA39F8672908FE0B638202DDBB7E2E678AD43CDDB |