Log Message:
py-dogpile-cache: updated to 0.9.2

0.9.2:
[bug] [installation]
Ensured that the “pyproject.toml” file is not included in builds, as the \ 
presence of this file indicates to pip that a pep-517 installation process \ 
should be used. As this mode of operation appears to be not well supported by \ 
current tools / distros, these problems are avoided within the scope of \ 
dogpile.cache installation by omitting the file.

0.9.1:
[bug] [tests]
Added decorator module as a required testing dependency to tox.ini so that tests \ 
work when this is not pre-installed.

[bug] [redis]
Added option to the Redis backend RedisBackend.thread_local_lock, which when set \ 
to False will disable the use of a threading local by the redis module in its \ 
distributed lock service, which is known to interfere with the lock’s behavior \ 
when used in an “async” use case, within dogpile this would be when using \ 
the CacheRegion.async_creation_runner feature. The default is conservatively \ 
being left at True, but it’s likely this should be set to False in all cases, \ 
so a warning is emitted if this flag is not set to False in conjunction with the \ 
distributed lock. Added an optional argument to RedisBackend that specifies \ 
whether or not a thread-local Redis lock should be used. This is the default, \ 
but it breaks asynchronous runner compatibility.

0.9.0:
[feature]
Added logging facililities into CacheRegion, to indicate key events such as \ 
cache keys missing or regeneration of values. As these can be very high volume \ 
log messages, logging.DEBUG is used as the log level for the events. Pull \ 
request courtesy Stéphane Brunner.

0.8.0:
[bug] [setup]
Removed the “python setup.py test” feature in favor of a straight run of \ 
“tox”. Per Pypa / pytest developers, “setup.py” commands are in general \ 
headed towards deprecation in favor of tox. The tox.ini script has been updated \ 
such that running “tox” with no arguments will perform a single run of the \ 
test suite against the default installed Python interpreter.

[bug] [py3k]
Replaced the Python compatbility routines for getfullargspec() with a fully \ 
vendored version from Python 3.3. Originally, Python was emitting deprecation \ 
warnings for this function in Python 3.8 alphas. While this change was reverted, \ 
it was observed that Python 3 implementations for getfullargspec() are an order \ 
of magnitude slower as of the 3.4 series where it was rewritten against \ 
Signature. While Python plans to improve upon this situation, SQLAlchemy \ 
projects for now are using a simple replacement to avoid any future issues.

[bug] [installation]
Pinned minimum version of Python decorator module at 4.0.0 (July, 2015) as \ 
previous versions don’t provide the API that dogpile is using.

[bug] [py3k]
Fixed the sha1_mangle_key() key mangler to coerce incoming Unicode objects into \ 
bytes as is required by the Py3k version of this function.