Result for 447AA115CE8154BC1CEBA477704EF0D83CFDB1DC

Query result

Key Value
FileName./usr/lib/python3.6/site-packages/dogpile/cache/api.py
FileSize6347
MD5BED4646E2E34DF8B5547E5E77A4C480D
SHA-1447AA115CE8154BC1CEBA477704EF0D83CFDB1DC
SHA-256BCB89380735D9D4D9CBEDD37FC8A115CCD7E659443735927814E5763F6B7A22F
SHA-512FE5C7060173909C158612915D091C44117AF6514894F9EC2F2FA40CF02B9130AEEEC9AF9BE400138CC338D259EC15C81AA5F4D869AFAB70371413EB1E2C08DE6
SSDEEP96:otFEGOHli1AtbqBEvA2B22gSLphwqMxNKZigqWsqKj40pz0p5SNecGDjhDpxy:ochXAh2VwhxIi/UKjmnu
TLSHT118D1CA1BFF898FA24E4745722ABB9055EB15002F393020B4BDACD6A87F51A75D1F74C8
insert-timestamp1728978769.4656546
mimetypetext/x-python
sourcesnap:FFUeVIKJvkwp401LWNWizwSrnxmlg8R0_5
hashlookup:parent-total48
hashlookup:trust100

Network graph view

Parents (Total: 48)

The searched file hash is included in 48 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD533793CC2F8394D12B5E12FACDB0190BD
PackageArchnoarch
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.
PackageNamepython2-dogpile-cache
PackageRelease10.12
PackageVersion0.6.7
SHA-1013526239303502BC8F01E8EC9DA75621C0AFEA9
SHA-25607FA48CE92B698EA452F2A0DCAA7893A74A1C6F2C422FB129583C9A7375F7246
Key Value
MD555D7B23BDCAF5DE6F0CB9469B0D0142C
PackageArchnoarch
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.
PackageNamepython3-dogpile-cache
PackageReleasebp150.10.2
PackageVersion0.6.7
SHA-1073B2D76BC6397F004D0E62639002E3DA6794B48
SHA-256A4E4B3448A782718DDA499189E436A8D58889D2D480A74592D6E28C5D090370D
Key Value
MD5DDB083C4B36120D71576F16C6F76F55E
PackageArchnoarch
PackageDescriptionDogpile consists of two subsystems, one building on top of the other. dogpile provides the concept of a "dogpile lock", a control structure which allows a single thread of execution to be selected as the "creator" of some resource, while allowing other threads of execution to refer to the previous version of this resource as the creation proceeds; if there is no previous version, then those threads block until the object is available. dogpile.cache is a caching API which provides a generic interface to caching backends of any variety, and additionally provides API hooks which integrate these cache backends with the locking mechanism of dogpile. Overall, dogpile.cache is intended as a replacement to the Beaker 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.
PackageMaintainerFedora Project
PackageNamepython2-dogpile-cache
PackageRelease1.el8.1
PackageVersion0.6.8
SHA-10F7652B9674CF2F2C593B40DAD17D7FB7C0623CB
SHA-2565043A90EBE9CB7DFEDC7D354DC347A2845081C6BC9A81DD9ECAAB673CCAB9904
Key Value
MD59F5579702450CF79E36299880A1974BE
PackageArchnoarch
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.
PackageNamepython3-dogpile-cache
PackageReleaselp153.10.1
PackageVersion0.6.7
SHA-111E11D7C069BBAD76EF20F03BD7A63ACB68C00CE
SHA-256801F2ED3A9ADC9F03E9325C96B08660DE37C8AA08CCEE4E81A9861D14BBB63FA
Key Value
MD560E7E993DD90F33D7103E6B7EF2E8294
PackageArchnoarch
PackageDescriptionDogpile consists of two subsystems, one building on top of the other. dogpile provides the concept of a "dogpile lock", a control structure which allows a single thread of execution to be selected as the "creator" of some resource, while allowing other threads of execution to refer to the previous version of this resource as the creation proceeds; if there is no previous version, then those threads block until the object is available. dogpile.cache is a caching API which provides a generic interface to caching backends of any variety, and additionally provides API hooks which integrate these cache backends with the locking mechanism of dogpile. Overall, dogpile.cache is intended as a replacement to the Beaker 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.
PackageMaintainerpterjan <pterjan>
PackageNamepython2-dogpile-cache
PackageRelease1.mga7
PackageVersion0.6.8
SHA-11ECBA2CB82059A2DC27F9CE9EDC77C5F98889E8D
SHA-256796F729DD28FBC2DF7A020B9368835594661989959E8C561F61BB2AF9282A4B8
Key Value
MD5631EC5A1D42C7EB07ECD917A5D689632
PackageArchnoarch
PackageDescriptionA 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.
PackageMaintainerhttps://bugs.opensuse.org
PackageNamepython3-dogpile.cache
PackageReleaselp150.2.1
PackageVersion0.6.5
SHA-121A612919DE6622D7D064D44B8F9C5DE7D265770
SHA-2566F0829E716A02021DCFFB7CE0340455DC5A994D4F02A89D4B5929BB2C26E1E3A
Key Value
MD531EC520C7C2DD01290D5743F2D7B8ADB
PackageArchnoarch
PackageDescriptionA 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.
PackageNamepython3-dogpile.cache
PackageReleaselp151.1.2
PackageVersion0.6.6
SHA-12753B3FB5DCFA75A80FE3DF19F9CB4BA2E4F94C8
SHA-256D023CF25830EDE5572A50CDAC3E41692BDD0B3FFC9E3E403CCD2EA12E9576933
Key Value
MD5B3042C61A417223496BCC8F3B6A56EE2
PackageArchnoarch
PackageDescriptionA 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.
PackageMaintainerhttps://bugs.opensuse.org
PackageNamepython2-dogpile.cache
PackageReleaselp150.2.1
PackageVersion0.6.5
SHA-12831323D541FDCF5F89B98628E6877E8E7AF0AED
SHA-25697475927841A6533CEF878A734C65D2BAB138A917E32557EBA70A26DB9766615
Key Value
MD5957D7543834638926FF7D741E394DE1E
PackageArchnoarch
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.
PackageNamepython2-dogpile-cache
PackageReleaselp151.10.1
PackageVersion0.6.7
SHA-12900B5BCE5389F2DF0243D5901E79654F913BBA6
SHA-2566040A631393660B7B8CEF47964E890F9203589910F506D514E2D74A1E81FA485
Key Value
MD5B2454FEEF3375E5F0FE00FE248D47F66
PackageArchnoarch
PackageDescriptionA 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.
PackageNamepython2-dogpile.cache
PackageRelease1.2
PackageVersion0.7.1
SHA-1297F16B0920C88238E14F8B90F1C2C80A110AB66
SHA-256106E3E5F4B1A35AA5940EA62F22E1F9409FB954BE6F42065AF8164803291C2BC