Log message:
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.

Log message:
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.