Result for 05C225869E3EB922EA8E32A0B1134E3F850F7DD3

Query result

Key Value
FileName./usr/share/doc/python-dogpile.cache-doc/html/front.html
FileSize6371
MD5911C6E5D358331BD269D7942DDF8BD5C
SHA-105C225869E3EB922EA8E32A0B1134E3F850F7DD3
SHA-25669F77B211364D11817AC026A35D90B1321C55389E8DC120F1280087C6CE46A88
SSDEEP96:3wEDmSU3Q2D9ljmDnyOz+HV2YurQASWCclsuDay2DKjmVnycz+Y:gml+gDnhyHVh6+WCUlLMVn1yY
TLSHT110D1742748F45A37869342DEFAA11B39FC83841BE7062904B5FD866C0FC1E50890FB2B
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
FileSize101264
MD5BB4E1D676C49A828BE52E692152389E0
PackageDescriptioncaching front-end based on the Dogpile lock - doc 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 locking system (see http://pypi.python.org/pypi/dogpile.core), 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 (see 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. . This package provides the documentation.
PackageMaintainerDebian OpenStack <team+openstack@tracker.debian.org>
PackageNamepython-dogpile.cache-doc
PackageSectiondoc
PackageVersion1.1.4-2
SHA-1BEB35704215EBD27E5F2E6323578B1777B83AA2F
SHA-256145FFA1D636FD48FD90D2CD9DD8E3E253CA98BDDBBB723E35DA00782E2DF83CA