Changelog for python3-dogpile.cache-1.2.2-86.1.noarch.rpm :

* Mon Jul 10 2023 Dirk Müller - update to 1.2.2:
* Made use of pep-673 ``Self`` type for method chained methods such as .CacheRegion.configure and .ProxyBackend.wrap
* Mon May 29 2023 Dirk Müller - update to 1.2.1:
* Added py.typed file to root so that typing tools such as Mypy recognize dogpile as typed. Pull request courtesy Daverball.
* Tue May 09 2023 Dirk Müller - update to 1.2.0:
* Added new construct api.CantDeserializeException which can be raised by user-defined deserializer functions which would be passed to CacheRegion.deserializer, to indicate a cache value that can\'t be deserialized and therefore should be regenerated.
* Tue Jul 19 2022 Dirk Müller - update to 1.1.8:
* 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.
* Added MemcacheArgs.dead_retry and MemcacheArgs.socket_timeout to the dictionary of additional keyword arguments that will be passed directly to GenericMemcachedBackend().
* 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
* Wed Mar 30 2022 Luigi Baldoni - Update to version 1.1.5
* Added support for additional pymemcache HashClient parameters: retry_attempts, retry_timeout, and dead_timeout.
* Fri Dec 03 2021 Ben Greiner - Update requirements
* Mon Sep 06 2021 Steve Kowalik - Update to 1.1.4:
* [usecase] [memcached] Added support for pymemcache socket keepalive and retrying client.
* [bug] [general] Fixed Python 3.10 deprecation warning involving threading. Pull request
* [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.
* [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.
* [feature] [memcached] Added support for the pymemcache backend, using the \"dogpile.cache.pymemcache\" backend identifier.
* Thu Jun 17 2021 Dirk Müller - update to 1.1.3:
* rereleae, no changes
* Thu Apr 22 2021 Dirk Müller - update to 1.1.2:
* rerelease, no changes
* Wed Mar 10 2021 Dirk Müller - fix build for older distributions with old default-pytest
* Sun Jan 24 2021 Dirk Müller - skip building against python 3.6
* Wed Nov 25 2020 Matej Cepl - Update to 1.1.1: - 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. - 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.
* Mon Sep 21 2020 Dirk Mueller - update to 1.0.2:
* Added support for TLS connections to the bmemcached backend.
* 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.
* 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
* Thu Jul 30 2020 Dirk Mueller - skip python2 building - 0.9.2 is python 3.x only
* Tue Jun 02 2020 Dirk Mueller - update to 0.9.2: 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. Added option to the Redis backend :paramref:`.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 :paramref:`.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 :class:`.RedisBackend` that specifies whether or not a thread-local Redis lock should be used. This is the default, but it breaks asynchronous runner compatibility.