Connecting to kernel for python 3.10.0 failed
See original GitHub issueEnvironment data
- VS Code version: 1.64.0
- Jupyter Extension version (available under the Extensions sidebar): v2022.1.1001775990
- Python Extension version (available under the Extensions sidebar): v2022.0.1786462952
- OS (Windows | Mac | Linux distro) and version: Mac
- Python and/or Anaconda version: 3.10.0
- Type of virtual environment used (N/A | venv | virtualenv | conda | …): conda 4.11.0
- Jupyter server running: Local
Expected behaviour
When executing a jupyter notebook python cell, the cell should be executed
Actual behaviour
Connecting to kernel (Python 3.10.0): waiting for jupyter server
This was fine for Jupyter extension v2022.1.1001614873. This is also fine for python 3.9. Only failed with python 3.10 and last jupyter extension v2022.1.1001775990
Steps to reproduce:
Create an empty Jupyter notebook. Type some python code in a cell and try to execute it.
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]
- XXX
Logs
Output for Jupyter
in the Output
panel (View
→Output
, change the drop-down the upper-right of the Output
panel to Jupyter
)
XXX
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Running cells with Python 3.10 requires ipykernel installed
I get the error message: Running cells with 'Python 3.10.0 64 bit' requires ipykernel installed or requires an update .
Read more >How to fix Kernel Error or broken Python in Jupyter Notebook
TL;DW BELOW! If you delete or upgrade your python version, you might get a Kernel Error when trying to use Jupyter Notebooks!
Read more >How to Fix Kernel Error in Jupyter Notebook
A kernel error occurs basically when you try opening a python 3 file in the wrong directory. The truth is Jupyter and Python...
Read more >What to do when things go wrong - The Jupyter Notebook
Jupyter fails to start · Have you installed it? ;-) · If you're using a menu shortcut or Anaconda launcher to...
Read more >Changelog — Python 3.11.1 documentation
gh-99181: Fix failure in except* with unhashable exceptions. ... In 3.10.0 and 3.10.1 gen_func().send(0) is equivalent to gen_func().throw(TypeError(.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi again.
I have just installed python with conda but using condo-forge channel which install version 3.10.2 instead of 3.10.0.
Now, everything is fine. So I don’t really understand what is going on. Is it due to the difference of python version or in the additional packages version that are installed with condo-forge instead of the default channel.
So you can consider the issue closed Regards
Vincent
Yes I’m using latest version if conda, namely 4.11.0. For me, this is not related to the issue you have mentioned. The issue must be related somehow to conda but everything is fine if I revert to the previous version of jupyter extension so something must of change in the last release that block the connection to the jupyter server installed using conda. Regards Vincent