Closed megies closed 5 years ago
Closing as duplicate of #38
Reopening since I didn't see that the error was hidden in the details, and is in fact a different issue.
Do you have conda list
for an env that can reproduce the problem?
Just a minute, I'll try to reproduce one, sorry for only listing the env after resolution above..
FWIW, this conda environment does not have an issue:
conda list
conda info
I do see that you have pretty outdated notebook 5.0.0, when current is 5.7.0. My guess is that's the issue.
I went back with conda install --revision ..
, this is the env showing the problem (sorry its so bloated, it's my default sandbox env):
conda list --export
:
Updating to notebook 5.7.0 still shows the issue:
jupyter error traceback:
conda package plan for updating notebook
and conda info --export
after doing the notebook
update to 5.7.0:
I just noticed there are newer builds numer 1000
for pyzmq
but they are in a subchannel gcc7
and thus don't get served by conda install -c conda-forge ..
?
https://anaconda.org/conda-forge/pyzmq/files
Anyway, I now got a working env (see below) with pretty much everything on recent version numbers I think, so probably I just ran into a very unlucky combination of package versions (and an old version of one of jupyter_client
, jupyter_console
, jupyter_core
or notebook
might have been the culprit) and you might want to close this one, dunno.
jupyter=1.0.0=py_1
jupyter_client=5.2.3=py_1
jupyter_console=5.2.0=py27_1
jupyter_core=4.4.0=py_0
libsodium=1.0.16=h470a237_1
notebook=5.7.0=py27_1000
pyzmq=17.1.2=py27hae99301_0
tornado=4.5.3=py27_0
zeromq=4.2.5=hfc679d8_6
Full env:
I strongly suspect it was notebook 5.0
that was the culprit. That's from a while back, before some significant changes to tornado and pyzmq that needed updates in the notebook.
The 100X
builds are part of the conda-forge transition to new compilers. pyzmq is still building with the old toolchain compilers until the compiler transition is finished (so you should see 1001 on the gcc7 label and 1 on the main label shortly).
I think this can be closed, then.
I don't think it was notebook 5.0 alone, since it also happened with 5.7 (see here). But I agree that it's not worth it to put more time into this. Thanks for the help and sorry for stealing your time @minrk.
No problem! Sorry for causing trouble. We can chalk this up to "not sure exactly what combination is the problem, but if your packages are up-to-date it goes away" and move on.
Issue:
I have another (dependency?) versions clash, resulting in a broken installation. After updating
pyzmq
(and manually updatinglibsodium
see #38 and manually updatingtornado
) I am left with versions..Starting jupyter I get the following errors and the kernel does not start
Manually downgrading
zeromq
(which also downgradespyzmq
) resolves the problemAfter this jupyter runs without problems again.
Environment (
conda list
): (after resolving the problem)Details about
conda
and system (conda info
):