-
Notifications
You must be signed in to change notification settings - Fork 149
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
RuntimeWarning: coroutine 'ZMQSocketChannel.msg_ready' was never awaited #241
Comments
After a pip upgrade, I also hit this error
but none of them works and my jupyter console is broken. Any idea? |
After lots of trial-and-errors with different versions of pyzmq, prompt-toolkit, jupyter_client, jupyter_console, I've recovered jupyter-console. That was indeed a dependency hell problem. Unclear what the actual fix is. Maybe downgrading |
I have a similar issue; a Void Linux contributor has PR'ed an omnipus jupyter update and running PyZMQ is installed via the Edit: Void update PR: void-linux/void-packages#30873 |
I got same problem. python3 --versionPython 3.8.10 pip3 listPackage Version backcall 0.2.0 jupyter consoleJupyter console 6.4.0 Python 3.8.10 (default, Jun 2 2021, 10:49:15) In [1]: /usr/local/lib/python3.8/dist-packages/jupyter_console/ptshell.py:852: RuntimeWarning: coroutine 'ZMQSocketChannel.msg_ready' was never awaited Unhandled exception in event loop: Exception 'coroutine' object is not subscriptable |
On python3.7, downgrading from jupyter-client 7.0.1 to 6.1.12 worked for me. |
This fixed problem for me too -- ran into it when trying to startup It would be handy to know the underlying cause or if there's a long term solution to determine if I can consider emacs is viable jupyter interface for a project.. |
Getting the same issue in a fresh install of Ubuntu 21.04, python 3.9.5, using Anaconda as installer. Downgrading to 6.1.12 also worked for me ( |
For completeness (can't remember if I gave details), but I'm running Mint
20.1 (relatively fresh install) using stock python (not anaconda).
Downgrading via pip filxed for me as well. Also happy to help if I can..
…On Wed, Sep 22, 2021 at 2:59 AM muhark ***@***.***> wrote:
Getting the same issue in a fresh install of Ubuntu 21.04, python 3.9.5,
using Anaconda as installer. Downgrading to 6.1.12 also worked for me (conda
install jupyter_client=6.1). Let me know if there's any way I can help
address this issue.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#241 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATUE7KL3NSVU57ENLAPVJJDUDGLHXANCNFSM43F7KMPQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Same issue here! Mac OS 11.6. Homebrew Python 3.10.0 and 3.9.7, and Perl 5.34.0. Trying to use IPerl kernel. Fixed by downgrading jupyter_client to 6.1.12 via 3.10.0:
3.9.7:
|
Same issue on ubuntu 20. |
Per jupyter/jupyter_console#241 (comment) I'm not sure if this is directly related or not. Currently I know that nbconvert is part of the whole jupyter ecosystem, I think from the same developers. The error appears it a different location in the linked issue than what I'm getting in the CI pipeline, but I figure it's worth a shot before digging deeper.
In case further reports are welcome and/or useful, I've had this too for a while on Python 3.7.2 without conda on macOS 11.5.2. Jupyter Lab works fine, but the console gives
Some async stuff about the ZMQ messaging something something apparently. It's talking about tracemalloc, so
Does that make us any wiser by bring us to jupyter_console/jupyter_console/ptshell.py Line 852 in 64f1695
|
Isn't this fixed by #244? |
It appears it is. |
I had another issue a few days ago with my OSX (intel) with this. I had to downgrade my Python to from 3.10 to something below for jup_console to work. |
Reproduced on MacOs python3 -m venv env
source env/bin/activate
(env) pip install jupyter
(env) jupyter console
|
Reproduced macOS 12.2.1 (apple M1)
click to collapse
|
Upgrading to jupyter-console 6.4.3 should fix the issue. |
Yeah it's working for me now on macOS. Stellar, thank you. |
…upyter/jupyter_console#241 Former-commit-id: 1ed040590619991d51c7912f44b04330ffd8261c
Hello. When I run Jupyter console on Ubuntu 18.04, I get:
So far so good. But what the command I then type, I get:
Note that this is also the case with another kernel, and that Jupyter lab works. The problem seems to come from Jupyter console. Any idea how to handle this?
The text was updated successfully, but these errors were encountered: