saltbundlepy-pyzmq
PyZMQ is a lightweight and super-fast messaging library built on top of
the ZeroMQ library (http://www.zeromq.org).
-
1
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout systemsmanagement:saltstack:bundle:testing/saltbundlepy-pyzmq && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
_constraints | 0000000117 117 Bytes | |
pytest.ini | 0000000209 209 Bytes | |
pyzmq-23.2.0.tar.gz | 0001216729 1.16 MB | |
saltbundlepy-pyzmq-rpmlintrc | 0000000113 113 Bytes | |
saltbundlepy-pyzmq.changes | 0000028452 27.8 KB | |
saltbundlepy-pyzmq.spec | 0000004249 4.15 KB |
Revision 4 (latest revision is 6)
- Update to 23.2.0 * Use zmq.Event enums in parse_monitor_message for nicer reprs * Fix building bundled libzmq with ZMQ_DRAFT_API=1 * Fix subclassing zmq.Context with additional arguments in the constructor. Subclasses may now have full control over the signature, rather than purely adding keyword-only arguments * Typos and other small fixes - Release 23.1.0 * Fix global name of zmq.EVENT_HANDSHAKE_* constants * Fix constants missing when using import zmq.green as zmq * {func}zmq.utils.monitor.recv_monitor_msg now supports async Sockets. - Release 23.0.0 * all zmq constants are now available as Python enums (e.g. zmq.SocketType.PULL, zmq.SocketOption.IDENTITY), generated statically from zmq.h instead of at compile-time. This means that checks for the presence of a constant (hasattr(zmq, 'RADIO')) is not a valid check for the presence of a feature. This practice has never been robust, but it may have worked sometimes. Use direct checks via e.g. {func}zmq.has or {func}zmq.zmq_version_info. * A bit more type coverage of Context.term and Context.socket * Remove all use of deprecated stdlib distutils * Update to Cython 0.29.30 (required for Python 3.11 compatibility) * Compatibility with Python 3.11.0b1 * Switch to myst for docs * Deprecate zmq.utils.strtypes, now unused * Updates to autoformatting, linting - Fix rpmlint errors
Comments 0