Key | Value |
---|---|
FileName | ./usr/lib/python2.7/site-packages/dogpile/cache/util.pyo |
FileSize | 7686 |
MD5 | FE1B5068640C653A3BF3A8865E299A86 |
SHA-1 | 4B262D96A60C4536D3EE2BDC1B10E27F9E06DD21 |
SHA-256 | 6CD28761982A921A718932B5C1E5FC690EE6C72F7341D7498EA76D82B0A9D1B7 |
SSDEEP | 192:wseYINqs0bzHNCoYATgVRJShHoj4LUIG1:9enN7AsVDSVG4LU9 |
TLSH | T1BAF1FF80F3E84E5BDAA2547191F1022B9575F17372037742326C987A6CD83AAC93FBD1 |
hashlookup:parent-total | 6 |
hashlookup:trust | 80 |
The searched file hash is included in 6 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | BF5F30F2C80BACF8E723C81E7AB4325F |
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 | 2.fc23 |
PackageVersion | 0.5.5 |
SHA-1 | D5A5AEE57500A03247BD1DD1A57A031B3533C4AD |
SHA-256 | ADCCAD802332AC4FE60435C2D92877CCBD30D83E0FB4305393AEF094615D5FF7 |
Key | Value |
---|---|
MD5 | F1AEDACB6BAA8A492BC7539A7B14DFFE |
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.fc22 |
PackageVersion | 0.5.5 |
SHA-1 | 062312AF26075DC8859E49CD84E0B10CBE287375 |
SHA-256 | 2D65EE0BD46FBF5A21FE7CFE1295DF8880A96D26AD7A3F1DBC7A13FEA0FE866A |
Key | Value |
---|---|
MD5 | 409F5CD9CFF3A37213EC81F90A995F71 |
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.fc22 |
PackageVersion | 0.5.5 |
SHA-1 | 9818451DA8489E40257504374DA888E832D47FAA |
SHA-256 | 59C72254582E5F871B29CEC7B36429B9EA30AD9E289454585FC63C38F240BC8A |
Key | Value |
---|---|
MD5 | BE1960D8C6469C5566769261B06E16FD |
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 | 2.fc23 |
PackageVersion | 0.5.5 |
SHA-1 | 2458D76AB3676807CE726A13314E32FC5DF4E4C7 |
SHA-256 | 2EE3A707838025DBB032E8FC8B332C941FC434E606FE2ECD01D0D768F072189C |
Key | Value |
---|---|
MD5 | 6CD3DFDD5BB685181E042674014DEE97 |
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 | 2.fc23 |
PackageVersion | 0.5.5 |
SHA-1 | 1C6E5B2B426153A82BB6C74F77B10EF812342BE2 |
SHA-256 | 89C279A77F60EA617053EE2A0FDF72C1852B9D6F38D8270FF34EE7F63C5D6F41 |
Key | Value |
---|---|
MD5 | 5806D8C65248CE04EE7F09294585C4D1 |
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.fc22 |
PackageVersion | 0.5.5 |
SHA-1 | 28794038FCB6D5E47E9916DE1568516481877F39 |
SHA-256 | 76F2077F2228167D67E83470D5D17E2354FC5A01FFFC20A092FFF470183FC652 |