python-dogpile.cache

Edit Package python-dogpile.cache
No description set
Refresh
Refresh
Source Files
Filename Size Changed
dogpile.cache-0.9.2.tar.gz 0000329503 322 KB
python-dogpile.cache.changes 0000014852 14.5 KB
python-dogpile.cache.spec 0000002326 2.27 KB
Revision 24 (latest revision is 43)
Dominique Leuenberger's avatar Dominique Leuenberger (dimstar_suse) accepted request 810916 from Dirk Mueller's avatar Dirk Mueller (dirkmueller) (revision 24)
- 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.
Comments 0
openSUSE Build Service is sponsored by