Result for 205C55122A920DA751741A297616EF28706EC94B

Query result

Key Value
FileName./usr/lib/python2.6/site-packages/dogpile/cache/backends/memcached.py
FileSize10360
MD5923FA40A11C6E7C4DF060150782E81B0
SHA-1205C55122A920DA751741A297616EF28706EC94B
SHA-256EFDBD14F1B0B4EFC3F9D24E9C140CB952A354929DF8D60EA8A1F79F163BF4148
SSDEEP192:0MG/xLqX8Sbljb3hr1OjWJZq/BXJsKmiLUX+1G72tMZU5LOJjJGr4GWaEGW:O5LCbxL2nsKmiLUus248yGW
TLSHT13422660AEA0958F25B43895B5573E132A73E550737192434F8FCE35C0F1A86AC2EE9F8
hashlookup:parent-total13
hashlookup:trust100

Network graph view

Parents (Total: 13)

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

Key Value
MD54C8822C27DF58FB93EA71560ACCD8EAA
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.
PackageMaintainerFedora Project
PackageNamepython-dogpile-cache
PackageRelease1.el6
PackageVersion0.5.5
SHA-16DDFC1E538C75C1F36DDD9325A13F3293DFC9BAC
SHA-256414B8288D53FCC6B843425A0048CD2330E5002A5AD146A4331283170C484F3CB
Key Value
MD5A8E196C21B19D604B38AE40D7DF59CC8
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.
PackageMaintainerFedora Project
PackageNamepython3-dogpile-cache
PackageRelease1.fc22
PackageVersion0.5.5
SHA-148F4338A2BC715403EE0DE46B16DD8D8458FFE7E
SHA-25609DE50B72787958B0D1AB07486830B2C86D6AE00CD344F546E8F3FE55E7E93DD
Key Value
MD5BF5F30F2C80BACF8E723C81E7AB4325F
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.
PackageMaintainerFedora Project
PackageNamepython-dogpile-cache
PackageRelease2.fc23
PackageVersion0.5.5
SHA-1D5A5AEE57500A03247BD1DD1A57A031B3533C4AD
SHA-256ADCCAD802332AC4FE60435C2D92877CCBD30D83E0FB4305393AEF094615D5FF7
Key Value
MD5F1AEDACB6BAA8A492BC7539A7B14DFFE
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.
PackageMaintainerFedora Project
PackageNamepython-dogpile-cache
PackageRelease1.fc22
PackageVersion0.5.5
SHA-1062312AF26075DC8859E49CD84E0B10CBE287375
SHA-2562D65EE0BD46FBF5A21FE7CFE1295DF8880A96D26AD7A3F1DBC7A13FEA0FE866A
Key Value
MD5E9846DD3C3A18875085C09EBC251D8E8
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.
PackageMaintainerFedora Project
PackageNamepython3-dogpile-cache
PackageRelease2.fc23
PackageVersion0.5.5
SHA-18BD8B4B314A34577738269EAF674EC728C639398
SHA-256B11DF41D6C77E9BE04F72B7A7C41DC4EE56D97A5C4153484621732D8B00111BC
Key Value
MD5409F5CD9CFF3A37213EC81F90A995F71
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.
PackageMaintainerFedora Project
PackageNamepython-dogpile-cache
PackageRelease1.fc22
PackageVersion0.5.5
SHA-19818451DA8489E40257504374DA888E832D47FAA
SHA-25659C72254582E5F871B29CEC7B36429B9EA30AD9E289454585FC63C38F240BC8A
Key Value
MD5B0826A502E22921DAD9937377642DA0E
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.
PackageMaintainerFedora Project
PackageNamepython3-dogpile-cache
PackageRelease1.fc22
PackageVersion0.5.5
SHA-1E1ADEFFA68597E98C6EADAC40E851F569E4C4398
SHA-256036BD6504A752D9E66598A0D7281C1D7E6E196C84BD8510F7E0ADD952135A563
Key Value
MD5BE1960D8C6469C5566769261B06E16FD
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.
PackageMaintainerFedora Project
PackageNamepython-dogpile-cache
PackageRelease2.fc23
PackageVersion0.5.5
SHA-12458D76AB3676807CE726A13314E32FC5DF4E4C7
SHA-2562EE3A707838025DBB032E8FC8B332C941FC434E606FE2ECD01D0D768F072189C
Key Value
MD56CD3DFDD5BB685181E042674014DEE97
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.
PackageMaintainerFedora Project
PackageNamepython-dogpile-cache
PackageRelease2.fc23
PackageVersion0.5.5
SHA-11C6E5B2B426153A82BB6C74F77B10EF812342BE2
SHA-25689C279A77F60EA617053EE2A0FDF72C1852B9D6F38D8270FF34EE7F63C5D6F41
Key Value
MD55806D8C65248CE04EE7F09294585C4D1
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.
PackageMaintainerFedora Project
PackageNamepython-dogpile-cache
PackageRelease1.fc22
PackageVersion0.5.5
SHA-128794038FCB6D5E47E9916DE1568516481877F39
SHA-25676F2077F2228167D67E83470D5D17E2354FC5A01FFFC20A092FFF470183FC652
Key Value
MD508F89D390CA3A4D71B0BF81AD57CA40D
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.
PackageMaintainerFedora Project
PackageNamepython3-dogpile-cache
PackageRelease2.fc23
PackageVersion0.5.5
SHA-154FD7EF971B56333DE7C7E5A9BBB3848D51A19DF
SHA-2565AF2F8305326CC020B408C5F8D9AD278DFEB7B5FD2987EE65804CA2E583EA508
Key Value
MD5D617ADD9BF5CA31A1FA1F5C9578120EE
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.
PackageMaintainerFedora Project
PackageNamepython3-dogpile-cache
PackageRelease2.fc23
PackageVersion0.5.5
SHA-1DE7878DFBD708D6BBBADA0F338982CC2FCB2F4E2
SHA-256B57A8B2F758F801F8F54D23842670B20C386EF7458DA89150206227DE2F240B7
Key Value
MD5742BFFFB7096DB4E4F2A73322271D33E
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.
PackageMaintainerFedora Project
PackageNamepython3-dogpile-cache
PackageRelease1.fc22
PackageVersion0.5.5
SHA-1353B77E5BAA732864353A2D4EC005E8EF3B68CD0
SHA-2566871506F99BD5ABDDD8130CCF032E52F5CFBB2ED66671331CF9FE11A3733C8E7