forked from pool/python-dogpile.cache
- update to 0.6.8:
* Project hosting has moved to GitHub, under the SQLAlchemy
organization at https://github.com/sqlalchemy/dogpile.cache
* Fixed issue in the :meth:`.CacheRegion.get_or_create_multi` method which
was erroneously considering the cached value as the timestamp field if the
:meth:`.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`.
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-dogpile.cache?expand=0&rev=45
This commit is contained in:
@@ -1,3 +1,17 @@
|
||||
-------------------------------------------------------------------
|
||||
Thu Dec 6 05:44:25 UTC 2018 - Thomas Bechtold <tbechtold@suse.com>
|
||||
|
||||
- update to 0.6.8:
|
||||
* Project hosting has moved to GitHub, under the SQLAlchemy
|
||||
organization at https://github.com/sqlalchemy/dogpile.cache
|
||||
* Fixed issue in the :meth:`.CacheRegion.get_or_create_multi` method which
|
||||
was erroneously considering the cached value as the timestamp field if the
|
||||
:meth:`.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 :ticket:`38`.
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Tue Dec 4 12:47:28 UTC 2018 - Matej Cepl <mcepl@suse.com>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user