Result for 2105C9D77F81AC83B3872A789C2A0805A0E90B59

Query result

Key Value
FileName./usr/lib/python2.7/site-packages/dogpile/util/langhelpers.pyo
FileSize4946
MD5B53518C75FCC6EBB0A8101E1EFFABC17
SHA-12105C9D77F81AC83B3872A789C2A0805A0E90B59
SHA-256D9083A2BEB3FAEEC94B5285375CE1F3759181F275A6D47D9FC0C9CFF9B16C44A
SSDEEP96:tX8dxSItW4O1gCf/T7TmrRlYYEczfYMJmjXoYftIgQ1A:tsdYIlegCTmrRmYEc0Mojf1I1m
TLSHT137A1DC90F2F80967D6A554B194B0011F96B5F1B31206BB5323ACD87B28F839EC97BBC1
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

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

Key Value
MD560DAD7BB15875E6BC7A4C889F6C1B1FC
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. 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.
PackageMaintainerCBS <cbs@centos.org>
PackageNamepython-dogpile-cache
PackageRelease1.el7
PackageVersion0.6.2
SHA-10ACA7EEA1555566B546F410A742CF8DE32F2AF93
SHA-2562E81C59A3B2A1F8AA8235CE1C3C4E6DE483500DC6939E2EB06859DB3A8F13EA0