Script 'mail_helper' called by obssrc
Hello community,
here is the log from the commit of package python-pyzmq for openSUSE:Factory
checked in at 2022-09-27 20:13:01
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-pyzmq (Old)
and /work/SRC/openSUSE:Factory/.python-pyzmq.new.2275 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-pyzmq"
Tue Sep 27 20:13:01 2022 rev:51 rq:1005981 version:24.0.1
Changes:
--------
--- /work/SRC/openSUSE:Factory/python-pyzmq/python-pyzmq.changes
2022-08-18 16:49:04.825433780 +0200
+++ /work/SRC/openSUSE:Factory/.python-pyzmq.new.2275/python-pyzmq.changes
2022-09-27 20:13:02.713709846 +0200
@@ -1,0 +2,32 @@
+Sun Sep 25 20:35:28 UTC 2022 - Arun Persaud <a...@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 <a...@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.
+
+-------------------------------------------------------------------
Old:
----
pyzmq-23.2.1.tar.gz
New:
----
pyzmq-24.0.1.tar.gz
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ python-pyzmq.spec ++++++
--- /var/tmp/diff_new_pack.Xp8nsV/_old 2022-09-27 20:13:03.397711354 +0200
+++ /var/tmp/diff_new_pack.Xp8nsV/_new 2022-09-27 20:13:03.397711354 +0200
@@ -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
++++++ pyzmq-23.2.1.tar.gz -> pyzmq-24.0.1.tar.gz ++++++
++++ 7691 lines of diff (skipped)
