saltbundlepy-pyzmq

Edit Package saltbundlepy-pyzmq

PyZMQ is a lightweight and super-fast messaging library built on top of
the ZeroMQ library (http://www.zeromq.org).

Refresh
Refresh
Source Files
Filename Size Changed
_constraints 0000000117 117 Bytes
pytest.ini 0000000209 209 Bytes
pyzmq-24.0.1.tar.gz 0001219822 1.16 MB
saltbundlepy-pyzmq-rpmlintrc 0000000113 113 Bytes
saltbundlepy-pyzmq.changes 0000030480 29.8 KB
saltbundlepy-pyzmq.spec 0000004348 4.25 KB
Revision 5 (latest revision is 6)
Alexander Graul's avatar Alexander Graul (agraul) accepted request 1081268 from Pablo Suárez Hernández's avatar Pablo Suárez Hernández (PSuarezHernandez) (revision 5)
- skip numy tests for the testsuite on SLE15
- Fix build with OpenSSL 3.0 [bsc#1205042]
  * Temporarily disable test_on_recv_basic
- 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.
- 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.
- update to version 23.2.1:
  * Improvements:
    + First release with wheels for Python 3.11 (thanks
Comments 0
openSUSE Build Service is sponsored by