python/python-pyzmq
SHA256
14
0
Fork 0
forked from pool/python-pyzmq
Code Pull Requests Activity

Accepting request 1005944 from home:apersaud:branches:devel:languages:python

Browse Source 
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
This commit is contained in:
Dirk Mueller
2022-09-26 06:50:05 +00:00
committed by Git OBS Bridge
parent 1e2446ada8
commit c288e52fa5
4 changed files with 36 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

32
python-pyzmq.changes
View File

@@ -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>