spyder: Can't restart kernel due to content in stderr file
Issue 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 (kind of, I use the latest miniconda)
- Tried the other applicable steps from the Troubleshooting Guide
- Completed the Problem Description, Steps to Reproduce and Version sections below
Problem Description
Hi, I have been trying for some time to set up Spyder in a separate conda environment to the env I’m working in (to avoid conflicts). Currently I have installed Spyder 5.2.2 from conda-forge in my base environment, and set the Python interpreter in Preferences to another environment called mne. I’m having an issue that seems to be similar to #17042 - I can’t restart the kernel of the Spyder console (nothing happens if I try).
I also get “System nie może odnaleźć określonej ścieżki.” (which means “System cannot find specified path”) when the console starts, but I can write in the console after that. Resetting preferences fixes the problem, but it also changes the Python interpreter to the one that I don’t want to use (base env).
What steps reproduce the problem?
- Install spyder in a separate conda environment wrt the environemnt used for Spyder Python interpreter.
- Open spyder.
- Create any variable in the console (this step is not necessary).
- Choose “Restart kernel” option from the console “hambrger icon”.
- Accept by pressing “OK”.
- Nothing happens, the console still contains previous commands and the created variable is still present in the Variable Explorer. Any subsequent commands typed to the console also take effect as if the restart was ignored.
Versions
- Spyder version: 5.2.2
- Python version: 3.9.5
- Qt version: 5.12.9
- PyQt version: 5.12.3
- Operating System name/version: Windows 10
Dependencies
# Mandatory:
atomicwrites >=1.2.0 : 1.4.0 (OK)
chardet >=2.0.0 : 4.0.0 (OK)
cloudpickle >=0.5.0 : 2.0.0 (OK)
cookiecutter >=1.6.0 : 1.7.0 (OK)
diff_match_patch >=20181111 : 20200713 (OK)
intervaltree >=3.0.2 : 3.0.2 (OK)
IPython >=7.6.0;<8.0.0 : 7.31.1 (OK)
jedi >=0.17.2;<0.19.0 : 0.18.1 (OK)
jellyfish >=0.7 : 0.9.0 (OK)
jsonschema >=3.2.0 : 4.4.0 (OK)
keyring >=17.0.0 : 21.2.1 (OK)
nbconvert >=4.0 : 6.4.0 (OK)
numpydoc >=0.6.0 : 1.2 (OK)
paramiko >=2.4.0 : 2.9.2 (OK)
parso >=0.7.0;<0.9.0 : 0.8.3 (OK)
pexpect >=4.4.0 : 4.8.0 (OK)
pickleshare >=0.4 : 0.7.5 (OK)
psutil >=5.3 : 5.9.0 (OK)
pygments >=2.0 : 2.11.2 (OK)
pylint >=2.5.0 : 2.12.2 (OK)
pyls_spyder >=0.4.0 : 0.4.0 (OK)
pylsp >=1.3.2;<1.4.0 : 1.3.3 (OK)
pylsp_black >=1.0.0 : 1.0.1 (OK)
qdarkstyle =3.0.2 : 3.0.2 (OK)
qstylizer >=0.1.10 : 0.2.1 (OK)
qtawesome >=1.0.2 : 1.1.1 (OK)
qtconsole >=5.2.1;<5.3.0 : 5.2.2 (OK)
qtpy >=1.5.0 : 2.0.0 (OK)
rtree >=0.9.7 : None (NOK)
setuptools >=49.6.0 : 60.5.0 (OK)
sphinx >=0.6.6 : 4.3.2 (OK)
spyder_kernels >=2.2.1;<2.3.0 : 2.2.1 (OK)
textdistance >=4.2.0 : 4.2.2 (OK)
three_merge >=0.1.1 : 0.1.1 (OK)
watchdog >=0.10.3 : 2.1.6 (OK)
zmq >=17 : 22.3.0 (OK)
# Optional:
cython >=0.21 : None (NOK)
matplotlib >=2.0.0 : 3.5.0 (OK)
numpy >=1.7 : 1.21.2 (OK)
pandas >=1.1.1 : 1.3.5 (OK)
scipy >=0.17.0 : 1.7.3 (OK)
sympy >=0.7.3 : None (NOK)
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 18 (11 by maintainers)
Thanks @dalthviz, I’m currently away from the machine that caused the problem, so I will let you know in about 2 days.
@dalthviz I can check if downgrading
ipythonhelps. Let me know if there is something else I can do. Currently I can restart the console by closing it and opening another one. It’s not ideal, but I can live with it. 😃Thanks for directions @dalthviz @ccordoba12!
This is the output of
conda listfor the env used for Python Interpreter:output of conda list
The output of
spyder --debug-info verboseis pretty long, GitHub didn’t allow me to paste it to the comment, so I attach a text file. After restarting I get a lot of[spyder_kernels.comms.commbase] -> Call to unconnected comm: flush_std.spyder_log_restart_problem.txt
@ccordoba12 it restarts:
Hey @mmagnuski, thanks for reporting. This is very strange indeed, but I don’t think it’s related to issue #17042.
@dalthviz, could you check if this the case in a fresh conda-forge environment, using Python 3.9 on Windows? Thanks!