On Tue, Sep 25, 2018 at 1:10 AM, Björn Ketelaars <bjorn.ketela...@hydroxide.nl> wrote: > The recent [0] update of py-zmq to 17.1.2 breaks jupyter-notebook. > > I am unable to find a solution for this problem. I did find a > workaround: updating to a newer version of py-ipykernel. Elias M. > Mariani was so kind to provide a diff for updating our version in ports, > which has been OKed by edd@ [1]. However, this update breaks > py-matplotlib. The latter issue is fixed by updating py-matplotlib, > which relies on new DEPs... >
what a mess... :-( > > Way forward would be to: > 1.) Import py-kiwisolver (sent to ports@) > 2.) Import py-subprocess32 (sent to ports@) > 3.) Update py-matplotlib (diff sent to MAINTAINER) > 4.) Update py-ipykernel (OKed [1]) > > However, I'm not confident that there is enough time to test the above > before the 6.4 freeze. Therefore I would like to propose to revert the > recent update of py-zmq. Diff enclosed. let me ponder this for a few days before we revert py-zmq. I've done most of the same updates locally on my end so I'll compare my work with yours. I share your concern about updating matplotlib. It seems to be one of the trickier ports to get right. Question in the meantime. Does a slightly older version of matplotlib fix the problem for you? For example, 2.0.2? That version can avoid some of the risk of doing such a big update. For example, it doesn't depend on kiwisolver and subprocess32 is allegedly optional. I think if that version fixes the problem it would really minimize the risk of doing an update.
