PyZMQ 17.0.0 was released a few days ago. A version bump is desirable, as it might be required for newer ipython_client versions. Simply renaming the 16.0.2 ebuild is not sufficient, at least the test phase fails.
I can confirm that bump is needed for jupyter (tornado to be honest): jupyter-notebook Traceback (most recent call last): File "/usr/lib/python-exec/python3.6/jupyter-notebook", line 11, in <module> load_entry_point('notebook==5.2.1', 'console_scripts', 'jupyter-notebook')() File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 572, in load_entry_point return get_distribution(dist).load_entry_point(group, name) File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 2755, in load_entry_point return ep.load() File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 2408, in load return self.resolve() File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 2414, in resolve module = __import__(self.module_name, fromlist=['__name__'], level=0) File "/usr/lib64/python3.6/site-packages/notebook/notebookapp.py", line 43, in <module> ioloop.install() File "/usr/lib64/python3.6/site-packages/zmq/eventloop/ioloop.py", line 210, in install assert (not ioloop.IOLoop.initialized()) or \ AttributeError: type object 'IOLoop' has no attribute 'initialized'
emerges cleanly after changing ebuild name: Calculating dependencies... done! >>> Verifying ebuild manifests >>> Emerging (1 of 1) dev-python/pyzmq-17.0.0::local-overlay >>> Installing (1 of 1) dev-python/pyzmq-17.0.0::local-overlay >>> Jobs: 1 of 1 complete Load avg: 1.12, 0.66, 0.37 >>> Auto-cleaning packages... >>> No outdated packages were found on your system. * GNU info directory index is up-to-date. * After world updates, it is important to remove obsolete packages with * emerge --depclean. Refer to `man emerge` for more information.
But fails at runtime: jupyter-notebook Traceback (most recent call last): File "/usr/lib/python-exec/python3.6/jupyter-notebook", line 11, in <module> load_entry_point('notebook==5.2.1', 'console_scripts', 'jupyter-notebook')() File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 572, in load_entry_point return get_distribution(dist).load_entry_point(group, name) File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 2755, in load_entry_point return ep.load() File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 2408, in load return self.resolve() File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 2414, in resolve module = __import__(self.module_name, fromlist=['__name__'], level=0) File "/usr/lib64/python3.6/site-packages/notebook/notebookapp.py", line 42, in <module> from zmq.eventloop import ioloop File "/usr/lib64/python3.6/site-packages/zmq/__init__.py", line 47, in <module> from zmq import backend File "/usr/lib64/python3.6/site-packages/zmq/backend/__init__.py", line 40, in <module> reraise(*exc_info) File "/usr/lib64/python3.6/site-packages/zmq/utils/sixcerpt.py", line 34, in reraise raise value File "/usr/lib64/python3.6/site-packages/zmq/backend/__init__.py", line 27, in <module> _ns = select_backend(first) File "/usr/lib64/python3.6/site-packages/zmq/backend/select.py", line 26, in select_backend mod = __import__(name, fromlist=public_api) File "/usr/lib64/python3.6/site-packages/zmq/backend/cython/__init__.py", line 6, in <module> from . import (constants, error, message, context, ImportError: /usr/lib64/python3.6/site-packages/zmq/backend/cython/message.cpython-36m-x86_64-linux-gnu.so: undefined symbol: zmq_msg_group
Enabling USE "drafts" on zeromq solves undefined symbol problem. Sorry for the noise.
(In reply to Marius Brehler from comment #0) > PyZMQ 17.0.0 was released a few days ago. A version bump is desirable, as it > might be required for newer ipython_client versions. Simply renaming the > 16.0.2 ebuild is not sufficient, at least the test phase fails. Hi, A version bump is still desirable. Several python tools (e.g. jupiter, spyder) does currently not work without downgrading tornado, which gives other problems.
I had a pull request for a version bump at github, which got lost due to the repository troubles. Will open it again.
(In reply to Marius Brehler from comment #6) > I had a pull request for a version bump at github, which got lost due to the > repository troubles. Will open it again. If I interpret the discussion on Github correctly, there is a pull request for version bump that would solve the problems. Is there any way you could speed up the process a bit?
(In reply to Fredrik Fyring from comment #7) > (In reply to Marius Brehler from comment #6) > > I had a pull request for a version bump at github, which got lost due to the > > repository troubles. Will open it again. > > If I interpret the discussion on Github correctly, there is a pull request > for version bump that would solve the problems. Is there any way you could > speed up the process a bit? Yes, there is a pull request on Github. If there are no further requests, the PR is ready to get merged. Just pinged the python devs again.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=71763e055bbcdf37d8b18c4795dd6afcf8983e85 commit 71763e055bbcdf37d8b18c4795dd6afcf8983e85 Author: Marius Brehler <marbre@linux.sungazer.de> AuthorDate: 2018-07-23 10:14:22 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2018-08-14 20:45:34 +0000 dev-python/pyzmq: Version bump to 17.1.0 Bug: https://bugs.gentoo.org/648088 Closes: https://github.com/gentoo/gentoo/pull/9284 Package-Manager: Portage-2.3.40, Repoman-2.3.9 dev-python/pyzmq/Manifest | 1 + .../pyzmq/files/pyzmq-17.1.0-test_message.patch | 22 +++++++ dev-python/pyzmq/pyzmq-17.1.0.ebuild | 68 ++++++++++++++++++++++ 3 files changed, 91 insertions(+)