pkgsrc/devel/py-dogpile-cache/distinfo

$NetBSD: distinfo,v 1.2 2017/09/17 13:39:11 adam Exp $

SHA1 (dogpile.cache-0.6.4.tar.gz) = 437ecf8f6ac7bd03d54c2067f065fba1727617a7
RMD160 (dogpile.cache-0.6.4.tar.gz) = 73dd2ae9d9dce936849eb21441ef35b1d7f5ae71
SHA512 (dogpile.cache-0.6.4.tar.gz) = 0e86ed6aacbfbbbefdc3622ac956679c4986c77989daa3c3e845d4b8dbbf7945b4d0764789f03540b2ff59712e2ee86c8283cc3ee8d9e950f9ef1772db7ea137
Size (dogpile.cache-0.6.4.tar.gz) = 315533 bytes
py-dogpile-cache: update to 0.6.4 0.6.4 [bug] The method Region.get_or_create_multi() will not pass to the cache backend if no values are ultimately to be stored, based on the use of the Region.get_or_create_multi.should_cache_fn function. This empty dictionary is unnecessary and can cause API problems for backends like that of Redis. Pull request courtesy Tobias Sauerwein. [bug] The api.NO_VALUE constant now has a fixed __repr__() output, so that scenarios where this constant’s string value ends up being used as a cache key do not create multiple values. Pull request courtesy Paul Brown. [bug] A new exception class exception.PluginNotFound is now raised when a particular cache plugin class cannot be located either as a setuptools entrypoint or as a registered backend. Previously, a plain Exception was thrown. Pull request courtesy Jamie Lennox. 2017-09-17 15:39:11 +02:00			$NetBSD: distinfo,v 1.2 2017/09/17 13:39:11 adam Exp $
Import py-dogpile-cache-0.6.2 as devel/py-dogpile-cache Dogpile 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. 2017-04-14 15:53:25 +02:00
py-dogpile-cache: update to 0.6.4 0.6.4 [bug] The method Region.get_or_create_multi() will not pass to the cache backend if no values are ultimately to be stored, based on the use of the Region.get_or_create_multi.should_cache_fn function. This empty dictionary is unnecessary and can cause API problems for backends like that of Redis. Pull request courtesy Tobias Sauerwein. [bug] The api.NO_VALUE constant now has a fixed __repr__() output, so that scenarios where this constant’s string value ends up being used as a cache key do not create multiple values. Pull request courtesy Paul Brown. [bug] A new exception class exception.PluginNotFound is now raised when a particular cache plugin class cannot be located either as a setuptools entrypoint or as a registered backend. Previously, a plain Exception was thrown. Pull request courtesy Jamie Lennox. 2017-09-17 15:39:11 +02:00			`SHA1 (dogpile.cache-0.6.4.tar.gz) = 437ecf8f6ac7bd03d54c2067f065fba1727617a7`
			`RMD160 (dogpile.cache-0.6.4.tar.gz) = 73dd2ae9d9dce936849eb21441ef35b1d7f5ae71`
			`SHA512 (dogpile.cache-0.6.4.tar.gz) = 0e86ed6aacbfbbbefdc3622ac956679c4986c77989daa3c3e845d4b8dbbf7945b4d0764789f03540b2ff59712e2ee86c8283cc3ee8d9e950f9ef1772db7ea137`
			`Size (dogpile.cache-0.6.4.tar.gz) = 315533 bytes`