Key | Value |
---|---|
FileName | ./usr/lib/python3/dist-packages/dogpile/cache/util.py |
FileSize | 5679 |
MD5 | 38665E3E552C1461B8DCAD24EFF088E9 |
SHA-1 | 52ED7091FF53EA6163BCAF7D21CDA92060A3B09B |
SHA-256 | E364579A2E249D5EDF5EB722B0E345266D7E81C1C512D50B21DEFEB0074FC21D |
SSDEEP | 96:vo6F3Acgk7aoAsm6vJb1PfBRsGD4Am13b/xEFCXFkVlf1KsHY7n8WBm:vtAEnbzxQbZNoKCe8X |
TLSH | T1DAC14257AA9AE961C297C83B0457E423973B3E17241C1035BDFCE1A46F15A20C3F6EE9 |
hashlookup:parent-total | 21 |
hashlookup:trust | 100 |
The searched file hash is included in 21 parent files which include package known and seen by metalookup. A sample is included below:
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 | 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 | 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 | 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 |
Key | Value |
---|---|
MD5 | D8D66E6AB33392BDFB1068F3FF980D22 |
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 | 3.fc24 |
PackageVersion | 0.5.7 |
SHA-1 | 2E965CFCB610C81999147D27F454641BF6739219 |
SHA-256 | 8EF9ACB1FBFE29E413B8120E60ECF42FE1964AAB59E7F3805C1293D974C67DED |
Key | Value |
---|---|
MD5 | 918F3E0BECFB7FA239D97D5957F4347D |
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 | 3.fc24 |
PackageVersion | 0.5.7 |
SHA-1 | 32A1EFCCBD2605412F4FDB7078B7A8DDF9E56E40 |
SHA-256 | 3837BCBA54722102B43B190E7E101B29A06F9D146B405D86C60C8DFF2FD110DA |
Key | Value |
---|---|
MD5 | 742BFFFB7096DB4E4F2A73322271D33E |
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.fc22 |
PackageVersion | 0.5.5 |
SHA-1 | 353B77E5BAA732864353A2D4EC005E8EF3B68CD0 |
SHA-256 | 6871506F99BD5ABDDD8130CCF032E52F5CFBB2ED66671331CF9FE11A3733C8E7 |
Key | Value |
---|---|
FileSize | 29112 |
MD5 | 4DE8DAC01AB79451CBF52FFAAA170B78 |
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.7-1ubuntu1 |
SHA-1 | 395D86EEAE157B672BBDA72ACE6948E50D1FE907 |
SHA-256 | AA0C700732CE42CF710E613336EE5D0EB2A8809CECBCD52EB404C5890E05C6AB |
Key | Value |
---|---|
MD5 | A8E196C21B19D604B38AE40D7DF59CC8 |
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.fc22 |
PackageVersion | 0.5.5 |
SHA-1 | 48F4338A2BC715403EE0DE46B16DD8D8458FFE7E |
SHA-256 | 09DE50B72787958B0D1AB07486830B2C86D6AE00CD344F546E8F3FE55E7E93DD |
Key | Value |
---|---|
MD5 | 272D24835FB6A947978DD830867601AB |
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 | CBS <cbs@centos.org> |
PackageName | python-dogpile-cache |
PackageRelease | 1.el7 |
PackageVersion | 0.5.7 |
SHA-1 | 4D7235DD49CC7D48F5DEA98F1E3327E1C9874896 |
SHA-256 | 5B699A9527BD0F6E463B69867CC783C24A94C07C599C087D45DBB7FE697D1EFD |