Key | Value |
---|---|
FileName | ./usr/lib/python2.7/dist-packages/dogpile/cache/plugins/mako_cache.py |
FileSize | 2958 |
MD5 | 07E384298053141F61587169B981FE4E |
SHA-1 | 30E98D2552B3EBF50D10D4B77960AF26725EFF10 |
SHA-256 | 1736AD04FF9D919D2776D24E3C79B6B2353BAC88ACE4DB815C48BAF391B5B35A |
SSDEEP | 48:ZNs1+9lKHrX/wH4agASU7tYqDpcL76Av9lmfXEXz:MYLUntjU7Hpc/2u |
TLSH | T13D51AB5F9D098E93C2D3C4AF246AF091D93551233B845C75F3BED3A40F9092A46AF8E8 |
hashlookup:parent-total | 16 |
hashlookup:trust | 100 |
The searched file hash is included in 16 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | D761034134469AC39C4FB49A0D903D17 |
PackageArch | noarch |
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. |
PackageMaintainer | Fedora Project |
PackageName | python3-dogpile-cache |
PackageRelease | 1.fc20 |
PackageVersion | 0.5.0 |
SHA-1 | 0357C6DCAA154DA5DA8C7CE338F66EDAA9C6D91F |
SHA-256 | E5446AC8B8382535A613287590C8DFBCFB198E8087E1B0BB52EED0C2ED1D07EA |
Key | Value |
---|---|
MD5 | D7EB165256C3070F8263261657849189 |
PackageArch | noarch |
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. |
PackageMaintainer | Fedora Project |
PackageName | python-dogpile-cache |
PackageRelease | 1.fc21 |
PackageVersion | 0.5.4 |
SHA-1 | 0929FEFF7318D69804063339C585D9DC0994A320 |
SHA-256 | 67EA69DA438C90C7ADDF56B664B8D0C2D6D2A525AF47E7BE54F4FF6E878739B7 |
Key | Value |
---|---|
FileSize | 28838 |
MD5 | A8E8EE735CBC49904545EA1A9D6E7129 |
PackageDescription | caching front-end based on the Dogpile lock - Python 2.x 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 Python 2.x module. |
PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
PackageName | python-dogpile.cache |
PackageSection | python |
PackageVersion | 0.5.4-1ubuntu2 |
SHA-1 | 0C78FC8A5911A4E75B2B4B39DDC054BA6197FAAC |
SHA-256 | B090AC41BF7FA8EADBAEDD19DAEAE0CC8E0A9038EF197B8E9A0BB0FF1DB2AF2E |
Key | Value |
---|---|
MD5 | 0812DC2D4555DC6CC98CCF4DBBD1E593 |
PackageArch | noarch |
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. |
PackageMaintainer | Fedora Project |
PackageName | python3-dogpile-cache |
PackageRelease | 1.fc21 |
PackageVersion | 0.5.4 |
SHA-1 | 372E3D220DF59BFC0BEBE0361894FF2D2F48F883 |
SHA-256 | 54BCEE62664A4C35BBC1322B219E62A4150FBF9CE03DDC54FC0187F0BBC81199 |
Key | Value |
---|---|
FileSize | 28530 |
MD5 | 6A2611251E28EFD264C8BCFE17054CB4 |
PackageDescription | caching API built around the concept of a "dogpile lock" A cache API built around the concep of a "dogpile lock", which allows continued access to an expiring data value with a single thread generates a new value. |
PackageMaintainer | Chuck Short <zulcss@ubuntu.com> |
PackageName | python-dogpile.cache |
PackageSection | python |
PackageVersion | 0.5.0-0ubuntu2 |
SHA-1 | 3A147A6A42C62813C810181E63EEBBFB680E1B91 |
SHA-256 | C4D7001661EF36503A412662BCCA0C915377AE8996D3AA2C96A1DB3E909713C5 |
Key | Value |
---|---|
MD5 | D01AA0B9EBBD7FBCE20DDB5EC91DFE9E |
PackageArch | noarch |
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. |
PackageMaintainer | Fedora Project |
PackageName | python-dogpile-cache |
PackageRelease | 1.fc20 |
PackageVersion | 0.5.0 |
SHA-1 | 3ECF8A79C56D411F720DB321449B1AE2D2C98C6E |
SHA-256 | D60E8A5888F0EB498D7AD351D04B81600104A03EE85C684294A91D3E51ECE7CE |
Key | Value |
---|---|
MD5 | 93D1854FA3B9C7E956A60ADFEB54CEF5 |
PackageArch | noarch |
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. |
PackageMaintainer | Fedora Project |
PackageName | python3-dogpile-cache |
PackageRelease | 1.fc21 |
PackageVersion | 0.5.4 |
SHA-1 | 71AF9E98217D17E4A2C9ADD957A20693C2CCAE58 |
SHA-256 | 1D3E30AD55877A53B094EA37935D53D4F387A881253737555A83698417A0BF5F |
Key | Value |
---|---|
MD5 | 29CE9D5BA2FF38DF63161EF1C5C355EA |
PackageArch | noarch |
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. |
PackageMaintainer | Fedora Project |
PackageName | python3-dogpile-cache |
PackageRelease | 1.fc20 |
PackageVersion | 0.5.0 |
SHA-1 | 7BFED51AC1E6A2AB9DDB2B0601825A3142931C90 |
SHA-256 | D40D1CC5E40FFC74508A5FB36A029F9101BCD1635C35C4E602BA563ADCC9E46C |
Key | Value |
---|---|
MD5 | 3D91BE0AF74527524CECFECDC38874B1 |
PackageArch | noarch |
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. |
PackageMaintainer | Fedora Project |
PackageName | python-dogpile-cache |
PackageRelease | 1.fc21 |
PackageVersion | 0.5.4 |
SHA-1 | 7EA9C8E4AC6565BD7D2E9F86CA041B5E6B3E6AD6 |
SHA-256 | A0F6EA40B25C7E0B0B147A4AA39F8672908FE0B638202DDBB7E2E678AD43CDDB |
Key | Value |
---|---|
FileSize | 28534 |
MD5 | F1C56C3DEF7395FB8B659CFBBA5F8BFA |
PackageDescription | caching front-end based on the Dogpile lock - Python 3.x 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 Python 3.x module. |
PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
PackageName | python3-dogpile.cache |
PackageSection | python |
PackageVersion | 0.5.4-1ubuntu2 |
SHA-1 | A07E80CA0F60D2F5368C5F4D45C79C1610988D73 |
SHA-256 | ED93D0CA981224E33BFB2C6B433C6521E9DB09388B425F40D22F05535B65F76C |