- update to 1.1.2:

- Fix a potential crash due to a reference counting error when Python
    subclasses of ``greenlet.greenlet`` were deallocated. The crash
    became more common on Python 3.10; on earlier versions, silent
    memory corruption could result.
  - Fix a leak of a list object when the last reference to a greenlet
    was deleted from some other thread than the one to which it
    belonged. For this to work correctly, you must call a greenlet API
    like ``getcurrent()`` before the thread owning the greenlet exits:
    this is a long-standing limitation that can also lead to the leak of
    a thread's main greenlet if not called; we hope to lift this
    limitation. Note that in some cases this may also fix leaks of
    greenlet objects themselves. See `issue 251
  - Python 3.10: Tracing or profiling into a spawned greenlet didn't
    work as expected. See `issue 256

OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-greenlet?expand=0&rev=59

greenlet-1.1.0.tar.gz

@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:c87df8ae3f01ffb4483c796fe1b15232ce2b219f0b18126948616224d3f658ee
-size 85043

greenlet-1.1.2.tar.gz

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e30f5ea4ae2346e62cedde8794a56858a67b878dd79f7df76a0767e356b1744a
+size 91224

python-greenlet.changes

@@ -1,3 +1,22 @@
+-------------------------------------------------------------------
+Sat Oct 16 19:07:41 UTC 2021 - Dirk Müller <dmueller@suse.com>
+
+- update to 1.1.2:
+  - Fix a potential crash due to a reference counting error when Python
+    subclasses of ``greenlet.greenlet`` were deallocated. The crash
+    became more common on Python 3.10; on earlier versions, silent
+    memory corruption could result.
+  - Fix a leak of a list object when the last reference to a greenlet
+    was deleted from some other thread than the one to which it
+    belonged. For this to work correctly, you must call a greenlet API
+    like ``getcurrent()`` before the thread owning the greenlet exits:
+    this is a long-standing limitation that can also lead to the leak of
+    a thread's main greenlet if not called; we hope to lift this
+    limitation. Note that in some cases this may also fix leaks of
+    greenlet objects themselves. See `issue 251
+  - Python 3.10: Tracing or profiling into a spawned greenlet didn't
+    work as expected. See `issue 256
+
 -------------------------------------------------------------------
 Mon Aug 30 11:46:34 UTC 2021 - pgajdos@suse.com
 

python-greenlet.spec

@@ -19,7 +19,7 @@
 
 %{?!python_module:%define python_module() python-%{**} python3-%{**}}
 Name:           python-greenlet
-Version:        1.1.0
+Version:        1.1.2
 Release:        0
 Summary:        Lightweight in-process concurrent programming
 License:        MIT