From c288e52fa538f4fd3b97f610f5edfa9d5269c246123c3dcd8aa730665e567164 Mon Sep 17 00:00:00 2001
From: Dirk Mueller <dmueller@suse.com>
Date: Mon, 26 Sep 2022 06:50:05 +0000
Subject: [PATCH] Accepting request 1005944 from
 home:apersaud:branches:devel:languages:python

update to latest version

OBS-URL: https://build.opensuse.org/request/show/1005944
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-pyzmq?expand=0&rev=106
---
 python-pyzmq.changes | 32 ++++++++++++++++++++++++++++++++
 python-pyzmq.spec    |  2 +-
 pyzmq-23.2.1.tar.gz  |  3 ---
 pyzmq-24.0.1.tar.gz  |  3 +++
 4 files changed, 36 insertions(+), 4 deletions(-)
 delete mode 100644 pyzmq-23.2.1.tar.gz
 create mode 100644 pyzmq-24.0.1.tar.gz

diff --git a/python-pyzmq.changes b/python-pyzmq.changes
index 8b9c770..2489a0f 100644
--- a/python-pyzmq.changes
+++ b/python-pyzmq.changes
@@ -1,3 +1,35 @@
+-------------------------------------------------------------------
+Sun Sep 25 20:35:28 UTC 2022 - Arun Persaud <arun@gmx.de>
+
+- update to version 24.0.1:
+  * Fix several possible resource warnings and deprecation warnings
+    when cleaning up contexts and sockets, especially in pyzmq's own
+    tests and when implicit teardown of objects is happening during
+    process teardown.
+
+-------------------------------------------------------------------
+Sat Sep 17 15:41:41 UTC 2022 - Arun Persaud <arun@gmx.de>
+
+- update to version 24.0.0:
+  * Breaking changes:
+    + Due to a libzmq bug causing unavoidable crashes for some users,
+      Windows wheels no longer bundle libzmq with AF_UNIX support. In
+      order to enable AF_UNIX on Windows, pyzmq must be built from
+      source, linking an appropriate build of libzmq
+      (e.g. libzmq-v142). AF_UNIX support will be re-enabled in pyzmq
+      wheels when libzmq published fixed releases.
+    + Using a {class}zmq.Context as a context manager or deleting a
+      context without closing it now calls {meth}zmq.Context.destroy
+      at exit instead of {meth}zmq.Context.term. This will have little
+      effect on most users, but changes what happens when user bugs
+      result in a context being implicitly destroyed while sockets are
+      left open. In almost all cases, this will turn what used to be a
+      hang into a warning. However, there may be some cases where
+      sockets are actively used in threads, which could result in a
+      crash. To use sockets across threads, it is critical to properly
+      and explicitly close your contexts and sockets, which will
+      always avoid this issue.
+
 -------------------------------------------------------------------
 Wed Aug 17 03:13:44 UTC 2022 - Arun Persaud <arun@gmx.de>
 
diff --git a/python-pyzmq.spec b/python-pyzmq.spec
index 554d1f4..3d15053 100644
--- a/python-pyzmq.spec
+++ b/python-pyzmq.spec
@@ -26,7 +26,7 @@
 %bcond_with     tests
 %endif
 Name:           python-pyzmq
-Version:        23.2.1
+Version:        24.0.1
 Release:        0
 Summary:        Python bindings for 0MQ
 License:        BSD-3-Clause AND LGPL-3.0-or-later
diff --git a/pyzmq-23.2.1.tar.gz b/pyzmq-23.2.1.tar.gz
deleted file mode 100644
index f014802..0000000
--- a/pyzmq-23.2.1.tar.gz
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:2b381aa867ece7d0a82f30a0c7f3d4387b7cf2e0697e33efaa5bed6c5784abcd
-size 1218264
diff --git a/pyzmq-24.0.1.tar.gz b/pyzmq-24.0.1.tar.gz
new file mode 100644
index 0000000..9be7d3a
--- /dev/null
+++ b/pyzmq-24.0.1.tar.gz
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:216f5d7dbb67166759e59b0479bca82b8acf9bed6015b526b8eb10143fb08e77
+size 1219822