[MacPorts] #43272: py33-zmq @14.1.1 +universal and arch -i386 ipython notebook error
MacPorts
noreply at macports.org
Tue Sep 1 11:38:55 UTC 2026
#43272: py33-zmq @14.1.1 +universal and arch -i386 ipython notebook error
--------------------------+----------------------
Reporter: wrighteap@… | Owner: jrjsmrtn
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.2.1
Resolution: | Keywords:
Port: py-zmq |
--------------------------+----------------------
Comment (by jrjsmrtn):
I am the assignee here, and I am proposing this be closed as outdated.
The configuration in the report no longer exists:
● py33-zmq is gone. py-zmq now builds python.versions 27 310 311 312 313
314,
│ so there is no 3.3 subport to reproduce against. (The python33 port
itself still
│ exists at 3.3.7, but py-zmq no longer targets it.)
● The version is far behind. This is against py-zmq @14.1.1; the port is
now on the
│ 27.x series.
● arch -i386 is not available on current systems. universal_archs defaults
to
│ arm64 x86_64, and 32-bit Intel binaries do not run on modern macOS. The
failure as
│ described cannot be exercised there.
The ticket also has no technical history to lose. In eleven years the
three comments are
a request to Cc maintainers, an acknowledgement of it, and a "Cc Me!" —
nobody has
diagnosed the ImportError from zmq.utils.initthreads.
If anyone still hits an ImportError from py*-zmq under +universal on a
supported
system, a fresh ticket with a current reproducer would be far more useful
than reviving
this one.
Separately: I am stepping down as a maintainer of py-zmq
(https://github.com/macports/macports-ports/pull/34376), so I should not
remain the
assignee here in any case.
--
Ticket URL: <https://trac.macports.org/ticket/43272#comment:5>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list