question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Missing spyder‑kernels -- reinstalling to no avail

See original GitHub issue

Issue Report Checklist

  • [ x] Searched the issues page for similar reports Issue #7842 is very similar.
  • [ x] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
  • [ x] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
  • [x ] Tried basic troubleshooting (if a bug/error)
    • [x ] Restarted Spyder
    • [ x] Reset preferences with spyder --reset
    • [ x] Reinstalled the latest version of Anaconda
    • [x ] Tried the other applicable steps from the Troubleshooting Guide
  • [ x] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description

I am getting following after having reinstalled spyder‑kernels in the appropriate environment. The spyder and python interpreter are also is in the same environment

Your Python environment or installation doesn't have the spyder‑kernels module or the right version of it installed (>= 1.9.1 and < 1.10.0). Without this module is not possible for Spyder to create a console for you.
...

What steps reproduce the problem?

  1. Install spyder in the base conda environment on Ubuntu 18, Python 3.7 / conda
  2. Install spyder in another non-base conda environment per this instruction
  3. Start Spyder

What is the expected output? What do you see instead?

working console

Paste Traceback/Error Below (if applicable)

QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old

Versions

Python 3.7.7 64-bit | Qt 5.9.6 | PyQt5 5.9.2 | Linux 5.3.0-51-generic

Dependencies


# Mandatory:
atomicwrites >=1.2.0           :  1.4.0 (OK)
chardet >=2.0.0                :  3.0.4 (OK)
cloudpickle >=0.5.0            :  1.4.1 (OK)
diff_match_patch >=20181111    :  20181111 (OK)
intervaltree                   :  None (OK)
IPython >=4.0                  :  7.13.0 (OK)
jedi =0.15.2                   :  0.15.2 (OK)
keyring                        :  None (OK)
nbconvert >=4.0                :  5.6.1 (OK)
numpydoc >=0.6.0               :  0.9.2 (OK)
parso =0.5.2                   :  0.5.2 (OK)
pexpect >=4.4.0                :  4.8.0 (OK)
pickleshare >=0.4              :  0.7.5 (OK)
psutil >=5.3                   :  5.7.0 (OK)
pygments >=2.0                 :  2.6.1 (OK)
pylint >=0.25                  :  2.5.0 (OK)
pyls >=0.31.9;<0.32.0          :  0.31.10 (OK)
qdarkstyle >=2.8               :  2.8.1 (OK)
qtawesome >=0.5.7              :  0.7.0 (OK)
qtconsole >=4.6.0              :  4.7.3 (OK)
qtpy >=1.5.0                   :  1.9.0 (OK)
rtree >=0.8.3                  :  0.9.4 (OK)
sphinx >=0.6.6                 :  3.0.3 (OK)
spyder_kernels >=1.9.1;<1.10.0 :  1.9.1 (OK)
watchdog                       :  None (OK)
xdg >=0.26                     :  0.26 (OK)
zmq >=17                       :  18.1.1 (OK)

# Optional:
cython >=0.21                  :  None (OK)
matplotlib >=2.0.0             :  3.1.3 (OK)
numpy >=1.7                    :  1.18.3 (OK)
pandas >=0.13.1                :  1.0.3 (OK)
scipy >=0.17.0                 :  None (OK)
sympy >=0.7.3                  :  None (OK)

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:16 (8 by maintainers)

github_iconTop GitHub Comments

3reactions
jimmy3142commented, May 21, 2020

Thanks for your reply @dalthviz.

I was using a custom path linking to Python version 3.8 so that I could use that version of Python from within the Spyder console, as the default version with Spyder appears to be 3.7? Not sure if that is advised or whether it is best to use the default interpreter?

I have updated the kernel as you suggested and it has worked.

2reactions
ccordoba12commented, Apr 6, 2021

I had spyder 4.x.x, it was working fine. but every launch, i was prompted to upgrade to 5.0.0.

You can select not showing that message again in the dialog that prompts to update. We inform users about new versions because (usually) they fix important problems present in previous ones. But it’s not mandatory to update.

I get the problem below after doing pip install --upgrade spyder

That’s a duplicate of issue #15091 and it’ll be fixed in our next version (5.0.1). You can safely ignore that message for now, it’s a false alarm.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Upgraded to Spyder 5 IDE for Python; Missing spyder-kernels
0). The instructions to fix this suggest installing the missing kernals using. conda install spyder-kernels=2.3 or pip install spyder-kernels ...
Read more >
Common Illnesses — Spyder 5 documentation
Spyder -Kernels not installed/incompatible¶. Spyder requires a supported version of the spyder-kernels package to be present in the working environment you want ...
Read more >
Spyder_Kernels >=2.0.1,<2.1.0: 2.0.1 (Nok) - ADocLib
Reproduced the issue after updating with conda update spyder (or pip , if not using Missing spyder‑kernels -- reinstalling to no avail #12709....
Read more >
Spyder: You have missing dependencies! parso
Hi, I'm new to manjaro. One of the first things I did was installing spyder sudo pacman -S spyder before I did sudo...
Read more >
Installing spyder IDE for ArcPro - Esri Community
If you have gone to the Spyder website, downloaded it directly and installed it then that was the wrong thing to do! Uninstall...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found