Result for 24F6E82FF8F33E8A7574101E8D7168F0ABA4C131

Query result

Key Value
FileName./usr/lib/python3.6/site-packages/dogpile/__pycache__/lock.cpython-36.pyc
FileSize4731
MD5F07BB93EFD28F65733E9DF591D925375
SHA-124F6E82FF8F33E8A7574101E8D7168F0ABA4C131
SHA-2567161F46A0E73130925DBF8BCE4EAD8AD8D081AA931C94C12884DA4CB9ED07C6E
SSDEEP96:j4LsN21CVfaByXB350Oq4cfwXG8ghNMgw9kP9LV:8PhCB3IfcGZ0F9o
TLSHT13CA174E9FE4157BEF913F3B7512A22E4A6B4D23B779940D5B40DC00AAF09A7042374D9
hashlookup:parent-total2
hashlookup:trust60

Network graph view

Parents (Total: 2)

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

Key Value
MD55FAAD25C374FA9B7C6CFC39D7C3B646D
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.
PackageNamepython3-dogpile-cache
PackageRelease13.39
PackageVersion1.0.1
SHA-110BB33D943AF4B4A5A584D698AC0D34649EB02AA
SHA-2565E1AECAB535DB1C3D8CCA641F0D21A12C55379A8A2DA4ABCDCF7D3E6DF00CBAB
Key Value
MD50E729058FC5304C5A0E5B702BBFDCBF7
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.
PackageNamepython3-dogpile-cache
PackageRelease13.28
PackageVersion1.0.1
SHA-16622422745BABD08ECF4FAEC2311265983D8C0C7
SHA-25684D33C679541A0668E65C4F134A336FC04707D53925065644137BBFF3817249E