NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI, #281 most downloaded on PyPI
Python bindings for 0MQ
Latest stable
27.3.0
Last release 18 days ago
04 Nov 2026
Release timing varies
gaps range from 2 weeks to 12 months
Most releases are documented
notes for 53 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
16 years old
108 releases · first in 2010
Drag across the ruler to compare, or tap a release to open it.
See release notes , or pyzmq on PyPI .
See release notes , or pyzmq on PyPI .
Your coding agent can read these notes before it upgrades. Set up the MCP server →
See release notes , or pyzmq on PyPI .
See release notes , or pyzmq on PyPI .
See release notes , or pyzmq on PyPI .
See release notes , or pyzmq on PyPI .
27.3 is a small release.
Add lots more type coverage (thanks @jorenham!)
Fix default compiler flags for bundled libsodium/libzmq in wheels on mac and linux, greatly improving default performance of CURVE security when installed from wheels.
Changes related to updating cibuildwheel:
Add wheels for PyPy 3.12
i686 wheels target manylinux_2_28 instead of 2_17 (manylinux2014)
PyPy wheels for PyPy 3.11 and 3.12 target pp80 instead of pp73
27.2 is a small release, mostly updating the build process and typing. Lots of new type coverage.
Add python3 -m zmq.curve_keygen entrypoint for creating curve key pairs
Require Python 3.9 (drops Python 3.8)
Stop building wheels for free-threaded CPython 3.13 (cp313t)
Add wheels for free-threaded CPython 3.15 (cp315t)
Fix builds on Windows with Visual Studio 2026
Fix builds with upcoming Cython release
Add more type coverage, fix some typing, typing compatibility with mypy 2.1
27.1.0 restores prior behavior where the constant zmq.DRAFT_API represents the actual availability of the draft API. This requires both libzmq and pyzmq to be built with drafts enabled, not just libzmq. Restores behavior prior to pyzmq 23. In pyzmq 23-27.0, zmq.DRAFT_API was a synonym for zmq.has("draft") . It is relatively rare that these two definitions differ, but not impossible (e.g. libzmq built with drafts enabled, but pyzmq not).
27.0.2 fixes a bug where bind/connect could fail with “Invalid Argument” (EINVAL) when Python is run in devmode or with PYTHONMALLOC=debug .
27.0.1 adds wheels for android and free-threaded Python 3.14 (314t) thanks to cibuildwheel 3.1, and adds wheels for free-threaded Python for Windows on ARM. There are no changes to pyzmq code in this release.
Breaking changes:
There are no breaking code or API changes, only changes in the supported platforms of Linux wheels:
musllinux is updated from 1_1 (alpine 3.12) to 1_2 (alpine 3.13)
manylinux glibc is updated from glibc 2.17 (2014) to 2.28 for most manylinux wheels (Python >=3.10)
The oldest Python manylinux wheels (Python <=3.9 and 32b i686 builds) are bumped from glibc 2.12 (2010) to 2.17 (2014)
New EXPERIMENTAL features:
Experimental support for accessing socket.FD (and thereby compatibility with asyncio) for draft thread-safe libzmq sockets. Relying on this produces a zmq.error.DraftFDWarning to communicate that support is experimental and may be removed.
Maintenance changes:
Two major changes are thanks to updating Cython to 3.1:
We now publish a wheel using the CPython 3.12 stable ABI. That means wheel installs should work for the unreleased CPython 3.14 and beyond. For the first time, the number of wheels published with pyzmq releases has decreased . Free-threaded Python doesn’t yet have a stable ABI, so free-threaded CPython 3.14t still needs to compile from source until PyPI allows wheels for 3.14t. Please let me know if this causes any problems!
We now publish free-threaded wheels for Windows (amd64 and win32, not yet arm)
See release notes , or pyzmq on PyPI .
See release notes , or pyzmq on PyPI .
See release notes , or pyzmq on PyPI .
See release notes , or pyzmq on PyPI .
See [release notes][], or [pyzmq on PyPI][].
See [release notes][], or [pyzmq on PyPI][].
See [release notes][], or [pyzmq on PyPI][].
See [release notes][], or [pyzmq on PyPI][].
See [release notes][], or [pyzmq on PyPI][].
See [release notes][], or [pyzmq on PyPI][].
New features:
Socket.recv_into for receiving directly into buffers.
Changes:
Removed some supposedly dead code for unsupported libzmq < 3.2
Modernized some Cython that users hopefully shouldn’t notice
Fixes:
Fix building bundled libzmq with cmake 4. You can workaround this with -C cmake.args="-DCMAKE_POLICY_VERSION_MINIMUM=3.14" in earlier versions
pyzmq 26.3 drops support for Python 3.7 and adds wheels for PyPy 3.11
The cffi backend can now be built on CPython by setting PYZMQ_BACKEND=cffi , e.g.
PYZMQ_BACKEND = cffi pip install -- no - binary pyzmq cffi pyzmq
This is not fully supported, but can be used for testing.
26.2.1 is a tiny bugfix release
Update bundled libsodium to 1.0.20
Some typing-related fixes for pyright and newer mypy versions
Fix PYZMQ_NO_BUNDLE option name when specified via cmake instead of environment variable
Fix missing socket.context reference when shadowing existing Sockets
Various updates to documentation and examples, especially discouraging use of insecure recv_pyobj without message authentication. recv_pyobj is NOT deprecated, but it is discouraged .
26.2 fixes some regressions introduced by the new build system in 26.0:
These changes all match the behavior of pyzmq 25.1.2:
include libzmq location in rpath when building from source
restore libsodium randombytes_close fix for bundled libzmq
Disable sometimes-broken IPC/EPOLL on Windows
Installing pyzmq from source on Windows should build with IPC enabled by default, but the Windows wheels on PyPI have it disabled because it produces unavoidable crashes for some users.
IPC support via epoll on Windows was disabled in pyzmq 24 due to crashes, this was reintroduced somewhat unintentionally via the new build system in 26.0 (there was a chance libzmq 4.3.5 would fix it), but unfortunately the crashes remain, so IPC is disabled again in 26.2. See issue #1981 for more details.
Windows wheels now statically link msvcp instead of bundling msvcp.dll, which could cause compatibility problems.
26.1.0 is the first release with wheels for CPython 3.13. Free-threading support in CPython 3.13 is experimental, but since libzmq sockets themselves aren’t threadsafe, pyzmq sockets should still be handled with locks.
pyzmq tests are no longer distributed as part of the package
fix CFFI backend compilation with -Werror=incompatible-pointer-types
Add Cython as build dependency for non-pypy, non-cpython implementations (fixes install on pyston)
When bundling libsodium, download from libsodium’s releases on GitHub instead of download.libsodium.org, which appears to error frequently.
Fix install from source with cmake < 3.21
pyzmq 26 is a small release, but with some big changes hopefully nobody will notice, except for some users (especially on Windows) where pyzmq releases did not work.
The highlights are:
The Cython backend has been rewritten using Cython 3’s pure Python mode.
The build system has been rewritten to use CMake via scikit-build-core instead of setuptools (setup.py is gone!).
Bundled libzmq is updated to 4.3.5, which changes its license from LGPL to MPL.
This means:
Cython >=3.0 is now a build requirement (if omitted, source distributions should still build from Cython-generated .c files without any Cython present)
pyzmq’s Cython backend is a single extension module, which should improve install size, import time, compile time, etc.
pyzmq’s Cython backend is now BSD-licensed, matching the rest of pyzmq.
The license of the libzmq library (included in pyzmq wheels) starting with 4.3.5 is now Mozilla Public License 2.0 (MPL-2.0).
when building pyzmq from source and it falls back on bundled libzmq, libzmq and libsodium are built as static libraries using their own build systems (CMake for libzmq, autotools for libsodium except on Windows where it uses msbuild) rather than bundling libzmq with tweetnacl as a Python Extension.
Using pyzmq with the legacy libzmq 2.x is no longer supported. The minimum required libzmq is 3.2.2.
Since the new build system uses libzmq and libsodium’s own build systems, evaluated at install time, building pyzmq with bundled libzmq from source should be much more likely to succeed on a variety of platforms than the previous method, where their build system was skipped and approximated as a Python extension. But I would also be very surprised if I didn’t break anything in the process of replacing 14 years of setup.py from scratch, especially cases like cross-compiling. Please report any issues you encounter building pyzmq.
See build docs for more info.
New :
Experimental support for wheels on windows-arm64
Socket.bind('tcp://ip:0') can be used as a context manager to bind to a random port. The resulting URL can be retrieved as socket.last_endpoint .
Add SyncSocket and SyncContext type aliases for the default Socket/Context implementations, since the base classes are Generics, type-wise. These are type aliases only to be used in type checking, not actual classes.
Enhancements :
repr(Frame) now produces a nice repr, summarizing Frame contents (without getting too large), e.g. <zmq.Frame(b'abcdefghijkl'...52B)>
Breaking changes :
str(Frame) no longer returns the whole frame contents interpreted as utf8-bytes. Instead, it returns the new summarized repr, which produces more logical results with print , etc. bytes(Frame) remains unchanged, and utf-8 text strings can still be produced with: bytes(Frame).decode("utf8") , which works in all versions of pyzmq and does the same thing.
Stop building Python 3.7 wheels for manylinux1, which reached EOL in January, 2022. The new build system doesn’t seem to be able to find cmake in that environment.
See [release notes][], or [pyzmq on PyPI][].
See [release notes][], or [pyzmq on PyPI][].
See [release notes][], or [pyzmq on PyPI][].
See [release notes][], or [pyzmq on PyPI][].
See [release notes][], or [pyzmq on PyPI][].
See [release notes][], or [pyzmq on PyPI][].
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
- zmq.auth.ioloop.IOLoopAuthenticator is deprecated in favor of zmq.auth.asyncio.AsyncioAuthenticator
Fix builds with some recent compilers and bundled libzmq
Fix builds with upcoming Cython 3.1
25.1.1 is the first stable release with Python 3.12 wheels.
Changes:
Allow Cython 0.29.35 to build Python 3.12 wheels (no longer require Cython 3)
Bugs fixed:
Fix builds on Solaris by including generated platform.hpp
Cleanup futures in Socket.poll() that are cancelled and never return
Fix builds with -j when numpy is present in the build env
pyzmq 25.1 mostly changes some packaging details of pyzmq, including support for installation from source on Python 3.12 beta 1.
Enhancements:
Include address in error message when bind/connect fail.
Packaging changes:
Fix inclusion of some test files in source distributions.
Add Cython as a build-time dependency in build-system.requires metadata, following current recommendations of the Cython maintainers. We still ship generated Cython sources in source distributions, so it is not a strict dependency for packagers using --no-build-isolation , but pip will install Cython as part of building pyzmq from source. This makes it more likely that past pyzmq releases will install on future Python releases, which often require an update to Cython but not pyzmq itself. For Python 3.12, Cython >=3.0.0b3 is required.
Fix handling of shadow sockets in ZMQStream when the original sockets have been closed. A regression in 25.0.0, seen with jupyter-client 7.
Tiny bugfix release that should only affect users of PUBHandler or pyzmq repackagers.
Fix handling of custom Message types in PUBHandler
Small lint fixes to satisfy changes in mypy
License files have been renamed to more standard LICENSE.BSD, LICENSE.LESSER to appease some license auto-detect tools.
New:
Added socket_class argument to zmq.Context.socket()
Support shadowing sockets with socket objects, not just via address, e.g. zmq.asyncio.Socket(other_socket) . Shadowing an object preserves a reference to the original, unlike shadowing via address.
in zmq.auth , CredentialsProvider callbacks may now be async.
ZMQStream callbacks may now be async.
Add zmq.ReconnectStop draft constants.
Add manylinux_2_28 wheels for x86_64 CPython 3.10, 3.11, and PyPy 3.9 (these are in addition to not instead of the manylinux_2014 wheels).
Fixed:
When ZMQStream is given an async socket, it now warns and hooks up events correctly with the underlying socket, so the callback gets the received message, instead of sending the callback the incorrect arguments.
Fixed toml parse error in pyproject.toml , when installing from source with very old pip.
Removed expressed dependency on py when running with pypy, which hasn’t been used in some time.
Deprecated:
zmq.auth.ioloop.IOLoopAuthenticator is deprecated in favor of zmq.auth.asyncio.AsyncioAuthenticator
As part of migrating toward modern pytest, zmq.tests.BaseZMQTestCase is deprecated and should not be used outside pyzmq.
python setup.py test is deprecated as a way to launch the tests. Just use pytest .
Removed:
Bundled subset of tornado’s IOLoop (deprecated since pyzmq 17) is removed, so ZMQStream cannot be used without an actual install of tornado.
Remove support for tornado 4, meaning tornado is always assumed to run on asyncio.
Nothing published for this version
Nothing published for this version
pyzmq 24 has two breaking changes (one only on Windows), though they are not likely to affect most users.
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.
pyzmq 24 has two breaking changes (one only on Windows), though they are not likely to affect most users.
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 zmq.Context as a context manager or deleting a context without closing it now calls zmq.Context.destroy() at exit instead of 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.
- First release with wheels for Python 3.11 (thanks cibuildwheel!).
Improvements:
First release with wheels for Python 3.11 (thanks cibuildwheel!).
linux aarch64 wheels now bundle the same libzmq (4.3.4) as all other builds, thanks to switching to native arm builds on CircleCI.
Fixes:
Some type annotation fixes in devices.
- Use zmq.Event enums in parse_monitor_message for nicer reprs
Improvements:
Use zmq.Event enums in parse_monitor_message for nicer reprs
Fixes:
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
Fixing some regressions in 23.0:
Fixing some regressions in 23.0:
Fix global name of zmq.EVENT_HANDSHAKE_* constants
Fix constants missing when using import zmq.green as zmq
Compatibility fixes:
zmq.utils.monitor.recv_monitor_message() now supports async Sockets.
Fix build with mingw
- Remove all use of deprecated stdlib distutils
Changes:
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. zmq.has() or zmq.zmq_version_info() .
A bit more type coverage of Context.term and Context.socket
Compatibility fixes:
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
Maintenance changes:
Switch to myst for docs
Deprecate zmq.utils.strtypes , now unused
Updates to autoformatting, linting
New wheels for PyPy 3.9
Manylinux wheels for CPython 3.10 are based on manylinux2014
Nothing published for this version
Nothing published for this version
- Fix strlcpy compilation issues on alpine, freebsd. Adds new build-time dependency on packaging .
Fixes:
Fix strlcpy compilation issues on alpine, freebsd. Adds new build-time dependency on packaging .
In event-loop integration: warn instead of raise when triggering callback on a socket whose context has been closed.
Bundled libzmq in wheels backport a patch to avoid crashes due to inappropriate closing of libsodium’s random generator when using CurveZMQ.
Changes:
New ResourceWarnings when contexts and sockets are closed by garbage collection, which can be a source of hangs and leaks (matches open files)
Fix bundling of wepoll on Windows.
Fix bundling of wepoll on Windows.
- deprecate zmq.utils.jsonapi and remove support for non-stdlib json implementations in send/recv_json . Custom serialization methods should be used i…
New features:
IPC support on Windows: where available (64bit Windows wheels and bundled libzmq when compiling from source, via wepoll), IPC should work on appropriate Windows versions.
Nicer reprs of contexts and sockets
Memory allocated by recv(copy=False) is no longer read-only
asyncio: Always reference current loop instead of attaching to the current loop at instantiation time. This fixes e.g. contexts and/or sockets instantiated prior to a call to asyncio.run .
ssh: $PYZMQ_PARAMIKO_HOST_KEY_POLICY can be used to set the missing host key policy, e.g. AutoAdd .
Fixes:
Fix memory corruption in gevent integration
Fix memoryview(zmq.Frame) with cffi backend
Fix threadsafety issue when closing sockets
Changes:
pypy Windows wheels are 64b-only, following an update in cibuildwheel 2.0
deprecate zmq.utils.jsonapi and remove support for non-stdlib json implementations in send/recv_json . Custom serialization methods should be used instead.
- asyncio: experimental support for Proactor eventloop if tornado 6.1 is available by running a selector in a background thread.
New features:
asyncio: experimental support for Proactor eventloop if tornado 6.1 is available by running a selector in a background thread.
Fixes:
Windows: fix type of socket.FD option in win-amd64
asyncio: Cancel timers when using HWM with async Sockets
Other changes:
Windows: update bundled libzmq dll URLs for Windows. Windows wheels no longer include concrt140.dll.
adopt pre-commit for formatting, linting
- Fix fork-safety bug in garbage collection thread (regression in 20.0) when using subprocesses.
Fix fork-safety bug in garbage collection thread (regression in 20.0) when using subprocesses.
Start uploading universal wheels for ARM Macs.
- Add workaround for bug in DLL loading for Windows wheels with conda Python >= 3.8
Add workaround for bug in DLL loading for Windows wheels with conda Python >= 3.8
- Fix type of Frame.bytes for non-copying recvs with CFFI backend (regression in 21.0)
Fix type of Frame.bytes for non-copying recvs with CFFI backend (regression in 21.0)
Add manylinux wheels for pypy
This is a major release due to changes in wheels and building on Windows. Code changes from 21.0 are minimal.
This is a major release due to changes in wheels and building on Windows. Code changes from 21.0 are minimal.
Some typing fixes
Bump bundled libzmq to 4.3.4
Strip unused symbols in manylinux wheels, resulting in dramatically smaller binaries. This matches behavior in v20 and earlier.
Windows CPython wheels bundle public libzmq binary builds, instead of building libzmq as a Python Extension. This means they include libsodium for the first time.
Our own implementation of bundling libzmq into pyzmq on Windows is removed, instead relying on delvewheel (or installations putting dlls on %PATH%) to bundle dependency dlls.
The (new in 21.0) Windows wheels for PyPy likely require the Windows vcredist package. This may have always been the case, but the delvewheel approach doesn’t seem to work.
Windows + PyPy is now the only remaining case where a wheel has libzmq built as an Extension. All other builds ship libzmq built using its own tooling, which should result in better, more stable builds.
- Fix wheels on macOS older than 10.15 (sets MACOSX_DEPLOYMENT_TARGET to 10.9, matching wheel ABI tag).
Fix wheels on macOS older than 10.15 (sets MACOSX_DEPLOYMENT_TARGET to 10.9, matching wheel ABI tag).
pyzmq-21.0.1 only changes CI configuration for Windows wheels (built with VS2017 instead of VS2019), fixing compatibility with some older Windows on a
pyzmq-21.0.1 only changes CI configuration for Windows wheels (built with VS2017 instead of VS2019), fixing compatibility with some older Windows on all Pythons and removing requirement of VC++ redistributable package on latest Windows and Python < 3.8.
There still appears to be a compatibility issue with Windows 7 that will be fixed ASAP. Until then, you can pin pip install pyzmq<21 .
There are no changes from 21.0.0 for other platforms.
pyzmq 21 is a major version bump because of dropped support for old Pythons and some changes in packaging. CPython users should not face major compati
pyzmq 21 is a major version bump because of dropped support for old Pythons and some changes in packaging. CPython users should not face major compatibility issues if installation works at all :) PyPy users may see issues with the new implementation of send/recv. If you do, please report them!
The big changes are:
drop support for Python 3.5. Python >= 3.6 is required
mypy type stubs, which should improve static analysis of pyzmq, especially for dynamically defined attributes such as zmq constants. These are new! Let us know if you find any issues.
support for zero-copy and sending bufferables with cffi backend. This is experimental! Please report issues.
More wheels!
linux-aarch64 on Python 3.7-3.9
wheels for pypy36, 37 on Linux and Windows (previously just mac)
We’ve totally redone the wheel-building setup, so let us know if you start seeing installation issues!
Packaging updates:
Require Python >= 3.6, required for good type annotation support
Wheels for macOS no longer build libzmq as a Python Extension, instead ‘real’ libzmq is built and linked to libsodium, bundled with delocate. This matches the longstanding behavior of Linux wheels, and should result in better performance.
Add manylinux wheels for linux-aarch64. These bundle an older version of libzmq than the rest.
Build wheels for python3.8, 3.9 with manylinux2010 instead of manylinux1. Wheels for older Pythons will still be built on manylinux1.
rework cffi backend in setup.py
All wheels are built on GitHub Actions (most with cibuildwheel) instead of Min’s laptop (finally!).
New features:
zero-copy support in CFFI backend ( send(copy=False) now does something).
Support sending any buffer-interface-providing objects in CFFI backend.
Bugs fixed:
Errors during teardown of asyncio Sockets
Missing MSVCP140.dll in Python 3.9 wheels on Windows, causing vcruntime-redist package to be required to use the Python 3.9 wheels for pyzmq 20.0
20.0 is a major version bump because of dropped support for old Pythons and some changes in packaging, but there are only small changes for users with
20.0 is a major version bump because of dropped support for old Pythons and some changes in packaging, but there are only small changes for users with relatively recent versions of Python.
Packaging updates:
Update bundled libzmq to 4.3.3
Drop support for Python < 3.5 (all versions of Python < 3.6 are EOL at time of release)
Require setuptools to build from source
Require Cython 0.29 to build from version control (sdists still ship .c files, so will never need Cython)
Respect $PKG_CONFIG env for finding libzmq when building from source
New features:
Socket.bind() and Socket.connect() can now be used as context managers.
Fixes:
Better error when libzmq is bundled and fails to be loaded.
Hold GIL while calling zmq_curve_ functions, which may fix apparent threadsafety issues.
- Regenerate Cython sources with 0.29.21 in sdists for compatibility with Python 3.9
Regenerate Cython sources with 0.29.21 in sdists for compatibility with Python 3.9
Handle underlying socket being closed in ZMQStream with warning instead of error
Improvements to socket cleanup during process teardown
Fix debug-builds on Windows
Avoid importing ctypes during startup on Windows
Documentation improvements
Raise AttributeError instead of ZMQError(EINVAL) on attempts to read write-only attributes, for compatibility with mocking
- Fix TypeError during garbage collection
Fix TypeError during garbage collection
Fix compilation with some C++ compilers
Fixes in tests and examples
- Cython backend: Build Cython extensions with language level “3str” (requires Cython 0.29)
Cython backend: Build Cython extensions with language level “3str” (requires Cython 0.29)
Cython backend: You can now cimport zmq
Asyncio: Fix memory leak in Poller
Log: Much improved logging in zmq.log.handlers (see Asynchronous Logging via PyZMQ )
Log: add python -m zmq.log entrypoint
Sources generated with Cython 0.29.15
cimport zmqzmq.log.handlers (see {doc}howto/logging)python -m zmq.log entrypoint- Fix race condition when shutting down ZAP thread while events are still processing (only affects tests)
Fix race condition when shutting down ZAP thread while events are still processing (only affects tests)
Publish wheels for Python 3.8 on all platforms
Stop publishing wheels for Python 3.4 on Windows
Sources generated with Cython 0.29.14
- Compatibility with Python 3.8 release candidate by regenerating Cython courses with Cython 0.29.13
Compatibility with Python 3.8 release candidate by regenerating Cython courses with Cython 0.29.13
bump bundled libzmq to 4.3.2
handle cancelled futures in asyncio
make zmq.Context.instance() fork-safe
fix errors in zmq.Context.destroy() when opening and closing many sockets
zmq.Context.instance fork-safezmq.Context.destroy when opening and closing many sockets- Compatibility with Python 3.8 prerelease by regenerating Cython sources with Cython 0.29.10.
Compatibility with Python 3.8 prerelease by regenerating Cython sources with Cython 0.29.10.
Fix language_level=2 in Cython sources, for compatibility with Cython 0.30
Show missing path for ENOENT errors on ipc connections.
Fixes installation from source on non-unicode locales with Python 3. There are no code changes in this release.
Fixes installation from source on non-unicode locales with Python 3. There are no code changes in this release.
One column per quarter.