Key | Value |
---|---|
FileName | ./usr/lib/python2.7/site-packages/dogpile/cache/proxy.pyc |
FileSize | 3889 |
MD5 | 395CC2722FC033CA94168A37C3F042A2 |
SHA-1 | 328ECC37BF857FA957AC9912F1F9397F79C63496 |
SHA-256 | 738E33DE40D878826F24F9C27E08D0AA4F611C6DE486010054EFB8CC43FB9903 |
SSDEEP | 96:jLuGsqXoHfqpPcFbj059NTsQVT6mHQHVTN:jLes+o8305jsQZ6SSZN |
TLSH | T130816281EB9A8E57EA7B497570F02226F97CE03B9303B74131AC61393F98245C93DAC5 |
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 |