Log message:
py-dogpile-cache: updated to 1.1.8

1.1.8

bug

[bug] [memcached]
Moved the MemcacheArgs.dead_retry argument and the MemcacheArgs.socket_timeout \ 
argument which were erroneously added to the “set_parameters”, where they \ 
have no effect, to be part of the Memcached connection arguments \ 
MemcachedBackend.dead_retry, MemcachedBackend.socket_timeout.

1.1.7

usecase

[usecase] [memcached]
Added MemcacheArgs.dead_retry and MemcacheArgs.socket_timeout to the dictionary \ 
of additional keyword arguments that will be passed directly to \ 
GenericMemcachedBackend().

1.1.6

usecase

[usecase] [redis]
Added RedisBackend.connection_kwargs parameter, which is a dictionary of \ 
additional keyword arguments that will be passed directly to StrictRedis() or \ 
StrictRedis.from_url(), in the same way that this parameter works with the \ 
RedisSentinelBackend already.

bug

[bug] [redis]
Fixed regression caused by backwards-incompatible API changes in Redis that \ 
caused the “distributed lock” feature to not function.

Log message:
py-dogpile-cache: updated to 1.1.5

1.1.5:
Unknown changes

Log message:
*: bump PKGREVISION for egg.mk users

They now have a tool dependency on py-setuptools instead of a DEPENDS

Log message:
py-dogpile-cache: fix py-stevedore path

Log message:
py-dogpile-cache: updated to 1.1.4

1.1.4
usecase

[usecase] [memcached]
Added support for pymemcache socket keepalive and retrying client.
See also PyMemcacheBackend.socket_keepalive
PyMemcacheBackend.enable_retry_client

bug

[bug] [general]
Fixed Python 3.10 deprecation warning involving threading

1.1.3
bug

[bug] [regression] [tests]
Repaired the test suite to work with the 5.x series of the decorator module, \ 
which now appears to make use of the __signature__ attribute.
[bug] [regression]
Fixed regression where ProxyBackend was missing several methods that were added \ 
as part of the 1.1 release.

1.1.2
feature

[feature] [region]
Added new region method CacheRegion.key_is_locked(). Returns True if the given \ 
key is subject to the dogpile lock, which would indicate that the generator \ 
function is running at that time. Pull request courtesy Bastien Gerard.

[feature] [memcached]
Added support for the pymemcache backend, using the \ 
"dogpile.cache.pymemcache" backend identifier. Pull request courtesy \ 
Moisés Guimarães de Medeiros.
See also PyMemcacheBackend

1.1.1
bug

[bug] [region]
Fixed regression where the serialization and deserialization functions could be \ 
inadvertently turned into instance methods with an unexpected argument \ 
signature, namely when pickle.dumps and pickle.loads are the pure Python version \ 
as is the case in pypy.

1.1.0
feature

[feature] [region]
Reworked the means by which values are serialized and deserialized from \ 
backends, and provided for custom serialization of values. Added the \ 
CacheRegion.serializer and CacheRegion.deserializer parameters which may be set \ 
to any serializer.
Serialization and deserialization now take place within the CacheRegion so that \ 
backends may now assume string values in all cases. This simplifies the existing \ 
backends and also makes custom backends easier to write and maintain.
Additionally, the serializer is now applied to the user-defined value portion of \ 
the CachedValue and not to the metadata or other portions of CachedValue object \ 
itself, so the serialized portion is effectively a “payload” within the \ 
larger CachedValue structure that is passed as part of the larger string format. \ 
The overall format is a separate JSON of the cached value metadata, followed by \ 
the serialized form. This allows for end-user serialization schemes that are \ 
hardwired to the values themselves without the need to serialize dogpile’s \ 
internal structures as well.
Existing custom backends should continue to work without issue; they now have \ 
the option to forego any separate serialization steps, and can also subclass a \ 
new backend BytesBackend that marks them as a backend that only deals with bytes \ 
coming in and out; all internal serialization logic from such a backend can be \ 
removed.
Pull request courtesy Alessio Bogon.

misc

[change]
Added pep-484 annotations to most of the dogpile.cache package.

1.0.2
feature

[feature] [memcached]
Added support for TLS connections to the bmemcached backend. Pull request \ 
courtesy Moisés Guimarães de Medeiros.
bug

[bug] [installation]
Repaired the setup.cfg file so that the source and wheel distributions will not \ 
add the “tests” directory to the Python environment. Pull request courtesy \ 
Michał Górny.

1.0.1
bug

[bug] [install]
dogpile.cache 1.0.0 was released with a minimum Python version of 3.5. However, \ 
due to a dependency issue, the minimum version is now Python 3.6. The 1.0.0 \ 
release will be removed from PyPI so that Python versions prior to 3.6 will \ 
continue to make use of the previous dogpile.cache 0.9.2.

[bug] [installation]
Removed the “universal=1” directive from setup.cfg as this would create \ 
py2/py3 wheels. dogpile 1.0.x is Python 3 only so a py3-only wheel is now \ 
created.

1.0.0
feature

[feature]
Improved plugin scanner performance by switching from pkg_resources to stevedore.
[feature] [redis]
Added support for Redis Sentinel. Pull request courtesy Stéphane Brunner. See \ 
RedisSentinelBackend.

misc

[change: py3k]
For version 1.0.0, dogpile.cache now supports Python 3.5 and above only.

Log message:
archivers: Replace RMD160 checksums with BLAKE2s checksums

All checksums have been double-checked against existing RMD160 and
SHA512 hashes

Could not be committed due to merge conflict:
devel/py-traitlets/distinfo

The following distfiles were unfetchable (note: some may be only fetched
conditionally):

./devel/pvs/distinfo pvs-3.2-solaris.tgz
./devel/eclipse/distinfo eclipse-sourceBuild-srcIncluded-3.0.1.zip

Log message:
devel: Remove SHA1 hashes for distfiles

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.

Log message:
py-dogpile-cache: updated to 0.7.1

0.7.1
[bug] [region] Fixed regression in 0.7.0 caused by 136 where the assumed \ 
arguments for the CacheRegion.async_creation_runner expanded to include the new \ 
CacheRegion.get_or_create.creator_args parameter, as it was not tested that the \ 
async runner would be implicitly called with these arguments when the \ 
CacheRegion.cache_on_arguments() decorator was used. The exact signature of \ 
async_creation_runner is now restored to have the same arguments in all cases.

0.7.0

[bug] The decorator module is now used when creating function decorators within \ 
CacheRegion.cache_on_arguments() and CacheRegion.cache_multi_on_arguments() so \ 
that function signatures are preserved. Pull request courtesy ankitpatel96.

Additionally adds a small performance enhancement which is to avoid internally \ 
creating a @wraps() decorator for the creator function on every get operation, \ 
by allowing the arguments to the creator be passed separately to \ 
CacheRegion.get_or_create().

[bug] [py3k] Fixed all Python 3.x deprecation warnings including inspect.getargspec()

Log message:
py-dogpile-cache: updated to 0.6.7

0.6.7:
[bug] Fixed issue in the CacheRegion.get_or_create_multi() method which was \ 
erroneously considering the cached value as the timestamp field if the \ 
CacheRegion.invalidate() method had ben used, usually causing a TypeError to \ 
occur, or in less frequent cases an invalid result for whether or not the cached \ 
value was invalid, leading to excessive caching or regeneration. The issue was a \ 
regression caused by an implementation issue in the pluggable invalidation \ 
feature added in 38.

0.6.6:
[feature] Added method CacheRegion.actual_backend which calculates and caches \ 
the actual backend for the region, which may be abstracted by the use of one or \ 
more ProxyBackend subclasses.
[bug] Fixed a condition in the Lock where the “get” function could be called \ 
a second time unnecessarily, when returning an existing, expired value from the \ 
cache.

0.6.5:
[bug] Fixed import issue for Python 3.7 where several variables named \ 
“async” were, leading to syntax errors. Pull request courtesy Brian Sheldon.