Connecting to kernel not going away
See original GitHub issueIssue Report Checklist
- Searched the issues page for similar reports
- Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
- Reproduced the issue after updating with
conda update spyder
(orpip
, if not using Anaconda) - Could not reproduce inside
jupyter qtconsole
(if console-related) - Tried basic troubleshooting (if a bug/error)
- Restarted Spyder
- Reset preferences with
spyder --reset
- Reinstalled the latest version of Anaconda
- Tried the other applicable steps from the Troubleshooting Guide
- Completed the Problem Description, Steps to Reproduce and Version sections below
Problem Description
IPython terminal keeps saying “Connecting to kernel”, so I can’t use the terminal. I have tried to look at other solutions people have come up with, but nothing has worked.
What steps reproduce the problem?
- Download Anaconda
- Open Anaconda Prompt and enter conda update --all
- Open Spyder 4
What is the expected output? What do you see instead?
I expect to use the terminal, but I keep seeing “Connecting to kernel”
Paste Traceback/Error Below (if applicable)
Unsure how to get the traceback
Versions
- Spyder version: 4.0.0
- Python version: 3.7.5
- Qt version: 5.7.9
- PyQt version: 5.9.2
- Operating System name/version: Windows 10
Dependencies
cloudpickle >=0.5.0 : 1.2.2 (OK)
pygments >=2.0 : 2.5.2 (OK)
qtconsole >=4.6.0 : 4.6.0 (OK)
nbconvert >=4.0 : 5.5.0 (OK)
sphinx >=0.6.6 : 2.3.0 (OK)
pylint >=0.25 : 2.3.1 (OK)
psutil >=0.3 : 5.6.7 (OK)
qtawesome >=0.5.7 : 0.6.0 (OK)
qtpy >=1.5.0 : 1.9.0 (OK)
pickleshare >=0.4 : 0.7.5 (OK)
zmq >=17 : 18.0.2 (OK)
chardet >=2.0.0 : 3.0.4 (OK)
numpydoc >=0.6.0 : 0.9.1 (OK)
spyder_kernels >=1.8.1;<2.0.0: 1.8.1 (OK)
qdarkstyle >=2.7 : 2.7 (OK)
atomicwrites >=1.2.0 : 1.3.0 (OK)
diff_match_patch >=20181111 : 20181111 (OK)
intervaltree : None (OK)
watchdog : None (OK)
keyring : None (OK)
pexpect >=4.4.0 : 4.7.0 (OK)
pympler : None (OK)
sympy >=0.7.3 : 1.4 (OK)
cython >=0.21 : None (NOK)
IPython >=4.0 : 7.6.1 (OK)
matplotlib >=2.0.0 : None (NOK)
pandas >=0.13.1 : None (NOK)
numpy >=1.7 : None (NOK)
scipy >=0.17.0 : None (NOK)
pyls >=0.31.2;<0.32.0 : 0.31.2 (OK)
rtree >=0.8.3 : 0.8.3 (OK)
Issue Analytics
- State:
- Created 4 years ago
- Comments:27 (12 by maintainers)
Top Results From Across the Web
jupyter connection to kernel hanging forever #5601 - GitHub
I can connect manually to the kernel and run python code. But , jupyter notebook cannot. Reasons ? 1) Tornado ?
Read more >Jupyter Notebook - Cannot Connect to Kernel - Stack Overflow
I uninstalled it with pip uninstall tornado then pip install tornado , which installed 6.2, and the issue was solved.
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 >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 >What to do when things go wrong - The Jupyter Notebook
As a result, when encountering kernel startup issues, again, check the argv stanza and verify it's pointing to a valid file. You may...
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
Thank you! What worked was I ran conda update conda from Mac’s terminal, and then spyder --reset.
Ok, great to know! At last!