Revisions of python-dogpile.cache
- update to 0.9.0 * Added logging facililities into :class:`.CacheRegion`
- Update to 0.7.1: * fix python3 deprecation warnings * Restore the API for async_creation_runner in all cases - Fix fdupes call
- 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`. - Remove superfluous devel dependency for noarch package
Automatic submission by obs-autosubmit
- skip lock tests, they fail frequently (bsc#1086987) - for testing purposes drop dogpile.cache-tests_more_slow_waiters.patch - only run generic tests using pytest (bsc#1089564)
- add dogpile-threading.patch
1
1
1
1
1
1
- update to 0.5.3: * Fixed bug where the key_mangler would get in the way of usage of the async_creation_runner feature within the :meth:` (forwarded request 213711 from dirkmueller)
- update to 0.5.2: * Added a new argument ``lock_factory`` to the :class:`.DBMBackend` * implementation. This allows for drop-in replacement of the default * :class:`.FileLock` backend, which builds on ``os.flock()`` and only * supports Unix platforms. (forwarded request 212462 from dirkmueller)
Displaying revisions 21 - 40 of 43