Key | Value |
---|---|
FileName | ./usr/lib/python3.3/site-packages/dogpile/cache/backends/file.py |
FileSize | 8535 |
MD5 | 37823A8FDD312DAECB428EB9E62BFF68 |
SHA-1 | 36A1C9CF272222F19AE0E1E751FE8F88A146EAA0 |
SHA-256 | 49150C4C65990FA8795AC33BB78F092A83713E356FC31344030AAC731AE473EF |
SSDEEP | 192:Pxd5INJ5HNEdXF3JFQUeQ1ODvI6oMgfGqmv:8HNEdXBbeQavIhho |
TLSH | T16D02941AAE6D5832C383D4A65D53E093E70EA84F160D523838FCE2546F1C968D1EADFC |
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 | 104BE1C645FF4B80E7F8EF21AC468EA5 |
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.fc19 |
PackageVersion | 0.4.2 |
SHA-1 | A7109CC3CEC34C5AF460A97FE7E69C86236D348B |
SHA-256 | 624FEA0B05D2B8ED2B0EC6D70AFE4385AB634BFED35933FA104E9E80C4D34B9D |
Key | Value |
---|---|
MD5 | 46F51DAD3B1C63292C99CFDAE8BB540E |
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.fc19 |
PackageVersion | 0.4.2 |
SHA-1 | 99CB90CE3A0420DF8050E9B6E1485936FCA1D7C9 |
SHA-256 | 7DAE84A674D2F14FF14BC7402C25B86E8A006AAB07CAADD461709DFA8328CCC4 |
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 |
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 | B8DB685605C0240220C522D4600E18EA |
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.fc19 |
PackageVersion | 0.4.2 |
SHA-1 | 01F6EE2DE96F561EDAB9DCA570712984F2624182 |
SHA-256 | A9B4C1BF247C88DC057FA12CEA74D4A5B8E9E52EC840E805977A77CB49728A03 |