Key | Value |
---|---|
FileName | ./usr/lib/python3.4/site-packages/dogpile/cache/backends/redis.py |
FileSize | 5743 |
MD5 | D1BC9481D62F409371F53265338352D5 |
SHA-1 | 8922576D9D2DA864A1CB8574ABE78149DE08D2F7 |
SHA-256 | B451474F3A44AEB9C53A1D42BB925EEDA64AE23491E481892BAAFE6FCC1CBCD5 |
SSDEEP | 96:odndMlm1yq9qlXJn2mtOiktOMqc/03JhEW67BHMqbK4x1hXvXxX:o7wm1yXlgrZgJTgBHdK+XvXxX |
TLSH | T1FCC1430A9D16C4631FD389A768B3E402B7394917334C2434B4BC96941F2EE3582EBEF8 |
hashlookup:parent-total | 10 |
hashlookup:trust | 100 |
The searched file hash is included in 10 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 |
---|---|
FileSize | 28056 |
MD5 | 29831A20E21189342E89DCD78EA3A05F |
PackageDescription | caching front-end based on the Dogpile lock - Python 3.x 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 locking system (see http://pypi.python.org/pypi/dogpile.core), 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 (see 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. . This package provides the Python 3.x module. |
PackageMaintainer | PKG OpenStack <openstack-devel@lists.alioth.debian.org> |
PackageName | python3-dogpile.cache |
PackageSection | python |
PackageVersion | 0.5.4-1 |
SHA-1 | B39598EFEF17FD48D59D06DE4608FCE291F3F0EB |
SHA-256 | EFCF27E8E1BA34F9C09A72B9A1BB6AE82C18FA3CF3951C321E88529042188440 |
Key | Value |
---|---|
FileSize | 28838 |
MD5 | A8E8EE735CBC49904545EA1A9D6E7129 |
PackageDescription | caching front-end based on the Dogpile lock - Python 2.x 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 locking system (see http://pypi.python.org/pypi/dogpile.core), 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 (see 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. . This package provides the Python 2.x module. |
PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
PackageName | python-dogpile.cache |
PackageSection | python |
PackageVersion | 0.5.4-1ubuntu2 |
SHA-1 | 0C78FC8A5911A4E75B2B4B39DDC054BA6197FAAC |
SHA-256 | B090AC41BF7FA8EADBAEDD19DAEAE0CC8E0A9038EF197B8E9A0BB0FF1DB2AF2E |
Key | Value |
---|---|
MD5 | 0812DC2D4555DC6CC98CCF4DBBD1E593 |
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 | 1.fc21 |
PackageVersion | 0.5.4 |
SHA-1 | 372E3D220DF59BFC0BEBE0361894FF2D2F48F883 |
SHA-256 | 54BCEE62664A4C35BBC1322B219E62A4150FBF9CE03DDC54FC0187F0BBC81199 |
Key | Value |
---|---|
MD5 | 0C76DB1D1EEB48A3A69F2F9CEADA3F4E |
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 | 1.fc21 |
PackageVersion | 0.5.4 |
SHA-1 | A58E1B4706F16DF4EE24363BC5C0F306E1C23536 |
SHA-256 | 13B7F51663CF528F35040020C946A5988715AA4FB9EA281BD52D73015B533658 |
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 |
Key | Value |
---|---|
FileSize | 28534 |
MD5 | F1C56C3DEF7395FB8B659CFBBA5F8BFA |
PackageDescription | caching front-end based on the Dogpile lock - Python 3.x 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 locking system (see http://pypi.python.org/pypi/dogpile.core), 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 (see 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. . This package provides the Python 3.x module. |
PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
PackageName | python3-dogpile.cache |
PackageSection | python |
PackageVersion | 0.5.4-1ubuntu2 |
SHA-1 | A07E80CA0F60D2F5368C5F4D45C79C1610988D73 |
SHA-256 | ED93D0CA981224E33BFB2C6B433C6521E9DB09388B425F40D22F05535B65F76C |
Key | Value |
---|---|
FileSize | 28374 |
MD5 | 657A0E9EF240C3086F8C65B4844358E9 |
PackageDescription | caching front-end based on the Dogpile lock - Python 2.x 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 locking system (see http://pypi.python.org/pypi/dogpile.core), 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 (see 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. . This package provides the Python 2.x module. |
PackageMaintainer | PKG OpenStack <openstack-devel@lists.alioth.debian.org> |
PackageName | python-dogpile.cache |
PackageSection | python |
PackageVersion | 0.5.4-1 |
SHA-1 | A81AAFDA701517533CD257209ADABE7B35736105 |
SHA-256 | 84F0B8D9663125FA48FD0B286F4E6B7087E21179B7E406275F6146848A855B58 |
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 | 93D1854FA3B9C7E956A60ADFEB54CEF5 |
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 | 1.fc21 |
PackageVersion | 0.5.4 |
SHA-1 | 71AF9E98217D17E4A2C9ADD957A20693C2CCAE58 |
SHA-256 | 1D3E30AD55877A53B094EA37935D53D4F387A881253737555A83698417A0BF5F |