Key | Value |
---|---|
CRC32 | B37BEC0B |
FileName | ./usr/share/doc/packages/python3-dogpile.cache/README.rst |
FileSize | 3357 |
MD5 | BF02E2278CE291CE6C9CA8B50AE71A37 |
OpSystemCode | {'MfgCode': '1006', 'OpSystemCode': '362', 'OpSystemName': 'TBD', 'OpSystemVersion': 'none'} |
ProductCode | {'ApplicationType': 'Server', 'Language': 'Multilanguage', 'MfgCode': '924', 'OpSystemCode': '599', 'ProductCode': '183706', 'ProductName': 'SUSE OpenStack Cloud x86_64 - 1 of 3', 'ProductVersion': '7'} |
SHA-1 | 12769B7488221B8203955453D39928EC4DC7E23D |
SHA-256 | DAB4C92D5634040D1AEC70644E4A694D526B9A27632CD48BF55F5C5F35CB349B |
SSDEEP | 96:g03KDeUWWjtkwLm1yTEBdQUyIVh20A6W1QufbYqOYJTLk:g0K6UdOwLJIth276LujTTLk |
SpecialCode | |
TLSH | T1D461623BFB0A17710B9346A5B96651B2EB3D406F77528085909E81F8385AC3583BFDF8 |
db | nsrl_modern_rds |
insert-timestamp | 1646984758.850228 |
source | NSRL |
hashlookup:parent-total | 31 |
hashlookup:trust | 100 |
The searched file hash is included in 31 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | 33793CC2F8394D12B5E12FACDB0190BD |
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. |
PackageName | python2-dogpile-cache |
PackageRelease | 10.12 |
PackageVersion | 0.6.7 |
SHA-1 | 013526239303502BC8F01E8EC9DA75621C0AFEA9 |
SHA-256 | 07FA48CE92B698EA452F2A0DCAA7893A74A1C6F2C422FB129583C9A7375F7246 |
Key | Value |
---|---|
MD5 | 55D7B23BDCAF5DE6F0CB9469B0D0142C |
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. |
PackageName | python3-dogpile-cache |
PackageRelease | bp150.10.2 |
PackageVersion | 0.6.7 |
SHA-1 | 073B2D76BC6397F004D0E62639002E3DA6794B48 |
SHA-256 | A4E4B3448A782718DDA499189E436A8D58889D2D480A74592D6E28C5D090370D |
Key | Value |
---|---|
MD5 | 60DAD7BB15875E6BC7A4C889F6C1B1FC |
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.6.2 |
SHA-1 | 0ACA7EEA1555566B546F410A742CF8DE32F2AF93 |
SHA-256 | 2E81C59A3B2A1F8AA8235CE1C3C4E6DE483500DC6939E2EB06859DB3A8F13EA0 |
Key | Value |
---|---|
MD5 | 9F5579702450CF79E36299880A1974BE |
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. |
PackageName | python3-dogpile-cache |
PackageRelease | lp153.10.1 |
PackageVersion | 0.6.7 |
SHA-1 | 11E11D7C069BBAD76EF20F03BD7A63ACB68C00CE |
SHA-256 | 801F2ED3A9ADC9F03E9325C96B08660DE37C8AA08CCEE4E81A9861D14BBB63FA |
Key | Value |
---|---|
MD5 | 631EC5A1D42C7EB07ECD917A5D689632 |
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. |
PackageMaintainer | https://bugs.opensuse.org |
PackageName | python3-dogpile.cache |
PackageRelease | lp150.2.1 |
PackageVersion | 0.6.5 |
SHA-1 | 21A612919DE6622D7D064D44B8F9C5DE7D265770 |
SHA-256 | 6F0829E716A02021DCFFB7CE0340455DC5A994D4F02A89D4B5929BB2C26E1E3A |
Key | Value |
---|---|
MD5 | 31EC520C7C2DD01290D5743F2D7B8ADB |
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. |
PackageName | python3-dogpile.cache |
PackageRelease | lp151.1.2 |
PackageVersion | 0.6.6 |
SHA-1 | 2753B3FB5DCFA75A80FE3DF19F9CB4BA2E4F94C8 |
SHA-256 | D023CF25830EDE5572A50CDAC3E41692BDD0B3FFC9E3E403CCD2EA12E9576933 |
Key | Value |
---|---|
MD5 | B3042C61A417223496BCC8F3B6A56EE2 |
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. |
PackageMaintainer | https://bugs.opensuse.org |
PackageName | python2-dogpile.cache |
PackageRelease | lp150.2.1 |
PackageVersion | 0.6.5 |
SHA-1 | 2831323D541FDCF5F89B98628E6877E8E7AF0AED |
SHA-256 | 97475927841A6533CEF878A734C65D2BAB138A917E32557EBA70A26DB9766615 |
Key | Value |
---|---|
MD5 | 957D7543834638926FF7D741E394DE1E |
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. |
PackageName | python2-dogpile-cache |
PackageRelease | lp151.10.1 |
PackageVersion | 0.6.7 |
SHA-1 | 2900B5BCE5389F2DF0243D5901E79654F913BBA6 |
SHA-256 | 6040A631393660B7B8CEF47964E890F9203589910F506D514E2D74A1E81FA485 |
Key | Value |
---|---|
MD5 | 5600AA24C3D110C88BD93214B55233C8 |
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. |
PackageName | python3-dogpile-cache |
PackageRelease | 10.1 |
PackageVersion | 0.6.7 |
SHA-1 | 2DB7BD4898A0F84B5DC2E0E40CA26ECCE4025E5B |
SHA-256 | 55E2EDD40D98A3EBEEAEF308320889157A13E1260B5F9874D1F7E541018EFFDC |
Key | Value |
---|---|
MD5 | C2B1D6A2DE89237B97EDD7F13E115926 |
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. |
PackageName | python2-dogpile.cache |
PackageRelease | lp150.2.1 |
PackageVersion | 0.6.4 |
SHA-1 | 3A60AD49EF87A69770FD9690FFCA8626951BC615 |
SHA-256 | 06AE63BD925044823E5894545C6B8D606B0ECF49AC8F4CE77C51CA702A846C9E |