-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not compatible with jupyter_client>=6
#151
Comments
Same error here
No problem with jupyter-client 5.3.4 |
Same. I think the way kernels are instantiated must have changed. Here's the issue's exit point from pweave: Pweave/pweave/processors/jupyter.py Line 35 in fa2a7f2
My guess is a difference in the jupyter_client.KernelManager. Looking at the diffs to jupyter_client.manager I'm a bit stumped - https://github.com/jupyter/jupyter_client/compare/0f13a70c920123237c804c68a7bb2f469da2ad0c..9f7c213 |
What I can say is that if you specify a kernel directly, it works. But you cannot do this from command line for pypublish 😢 |
A temporary fix seems to be to downgrade Native Python / Linux:
Anaconda, probably something like this (haven't tried):
Apparently not the first time this happend for Jupyter: |
I'll put up a PR to put an upper bound on the jupyter-client version. Maybe
it will get merged until a bigger fix to the kernel manager can be sorted.
…On Sun, Mar 8, 2020, 07:55 thirschbuechler ***@***.***> wrote:
A temporary fix seems to be to downgrade
Native Python / Linux:
sudo apt install python3-pip python3-setuptools
python3 -m pip install --upgrade jupyter_client==5.3.1
Anaconda, probably something like this (haven't tried):
conda install notebook==5.3.1
conda install jupyter_client==5.3.1
Apparently not the first time this happend for Jupyter:
jupyter/notebook#4937 <jupyter/notebook#4937>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#151?email_source=notifications&email_token=AB3P4L6FG3V7LBNLKZCJ4JTRGOBT3A5CNFSM4K2KLUQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOET7TY#issuecomment-596197327>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB3P4L5AXTRFPEJZ3DKYUJTRGOBT3ANCNFSM4K2KLUQA>
.up
|
jupyter_client>6
jupyter_client>=6
Everything seems to go back to normal with the release of jupyter-client 6.1.0. Environment : Windows10, python 3.7.5, jupyter-client 6.1.0 |
Interesting. I will try to test locally ... But the CI job looks like it may have some other issues basically in need of a lot of maintenance since the last release. |
I am still seeing the error on Mac OSX, python 3.7.6, jupyter-client 6.1.0 |
I upgraded from Python 3.7.5 to Python 3.8.2 and now I see a new error.
I applied the fix described here. I copied these lines at the beginning of
Everything now works as expected. |
It appears that the recent release of
jupyter_client
6.0.0 introduces a breaking changehttps://pypi.org/project/jupyter-client/#history
Environment Mac OS X, python 3.7.6
Also seen in linux environment on CI
The text was updated successfully, but these errors were encountered: