Hello community,

here is the log from the commit of package python-dogpile.cache for 
openSUSE:Factory checked in at 2020-06-10 00:45:59
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-dogpile.cache (Old)
 and      /work/SRC/openSUSE:Factory/.python-dogpile.cache.new.3606 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "python-dogpile.cache"

Wed Jun 10 00:45:59 2020 rev:24 rq:810916 version:0.9.2

Changes:
--------
--- 
/work/SRC/openSUSE:Factory/python-dogpile.cache/python-dogpile.cache.changes    
    2019-12-21 12:34:51.443462415 +0100
+++ 
/work/SRC/openSUSE:Factory/.python-dogpile.cache.new.3606/python-dogpile.cache.changes
      2020-06-10 00:46:02.534578230 +0200
@@ -1,0 +2,22 @@
+Tue Jun  2 17:00:19 UTC 2020 - Dirk Mueller <dmuel...@suse.com>
+
+- 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.
+
+-------------------------------------------------------------------

Old:
----
  dogpile.cache-0.9.0.tar.gz

New:
----
  dogpile.cache-0.9.2.tar.gz

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ python-dogpile.cache.spec ++++++
--- /var/tmp/diff_new_pack.2KM3YR/_old  2020-06-10 00:46:03.234579978 +0200
+++ /var/tmp/diff_new_pack.2KM3YR/_new  2020-06-10 00:46:03.234579978 +0200
@@ -1,7 +1,7 @@
 #
 # spec file for package python-dogpile.cache
 #
-# Copyright (c) 2019 SUSE LLC
+# Copyright (c) 2020 SUSE LLC
 #
 # All modifications and additions to the file contributed by third parties
 # remain the property of their copyright owners, unless otherwise agreed
@@ -19,7 +19,7 @@
 %{?!python_module:%define python_module() python-%{**} python3-%{**}}
 %define oldpython python
 Name:           python-dogpile.cache
-Version:        0.9.0
+Version:        0.9.2
 Release:        0
 Summary:        A caching front-end based on the Dogpile lock
 License:        BSD-3-Clause

++++++ dogpile.cache-0.9.0.tar.gz -> dogpile.cache-0.9.2.tar.gz ++++++
++++ 3487 lines of diff (skipped)


Reply via email to