spyder: "ERROR: execution aborted" after any exception, or line script.
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
- Tried the other applicable steps from the Troubleshooting Guide
- Completed the Problem Description, Steps to Reproduce and Version sections below
Problem Description
I have recently re-installed Anaconda and Spyder from scratch, since conda update conda did not work. After it, Spyder started to give me problems. Every now and then, probably 6 out 10 times a run a line/code the Console shots a ERROR: execution aborted, and I have to re-start the code from scratch.
What steps reproduce the problem?
- Running a single line or a full script.
- At any moment, in the beginning, running code chunks, or close to finish.
- I have to start from scratch every time.
What is the expected output? What do you see instead?
A smooth and clean run from beginning to end of my script.
Paste Traceback/Error Below (if applicable)
PASTE TRACEBACK HERE
Versions
- Spyder version: 4.1.4 py38_0
- Python version: 3.8.3 he1778fa_2
- Qt version: 5.9.7 vc14h73c81de_0
- PyQt version: 5.9.2 py38ha925a31_4
- Operating System name/version: Windows 10, x64bits
Dependencies
# Mandatory:
atomicwrites >=1.2.0 : 1.4.0 (OK)
chardet >=2.0.0 : 3.0.4 (OK)
cloudpickle >=0.5.0 : 1.5.0 (OK)
diff_match_patch >=20181111 : 20200713 (OK)
intervaltree : None (OK)
IPython >=4.0 : 7.16.1 (OK)
jedi =0.17.1 : 0.17.1 (OK)
nbconvert >=4.0 : 5.6.1 (OK)
numpydoc >=0.6.0 : 1.1.0 (OK)
paramiko >=2.4.0 : 2.7.1 (OK)
parso =0.7.0 : 0.7.0 (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 >=1.0 : 2.5.3 (OK)
pyls >=0.34.0;<1.0.0 : 0.34.1 (OK)
qdarkstyle >=2.8 : 2.8.1 (OK)
qtawesome >=0.5.7 : 0.7.2 (OK)
qtconsole >=4.6.0 : 4.7.5 (OK)
qtpy >=1.5.0 : 1.9.0 (OK)
rtree >=0.8.3 : 0.9.4 (OK)
sphinx >=0.6.6 : 3.1.2 (OK)
spyder_kernels >=1.9.2;<1.10.0 : 1.9.2 (OK)
watchdog : None (OK)
zmq >=17 : 19.0.1 (OK)
# Optional:
cython >=0.21 : 0.29.21 (OK)
matplotlib >=2.0.0 : 3.2.2 (OK)
numpy >=1.7 : 1.18.5 (OK)
pandas >=0.13.1 : 1.0.5 (OK)
scipy >=0.17.0 : 1.5.0 (OK)
sympy >=0.7.3 : 1.6.1 (OK)
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 16 (4 by maintainers)
I had the same issue I thought initially that my python version was having issues with the spyder interpreter, but it turned out that I was generating graphs not inline but automatic, this causes too many problems in my case, I do not know what the reason of that is but I changed to graphs inline in tools->preferences->IPython-console->Graphics->backend->inline. my debugger was not working either, but now it is working, I hope this is useful for some people.
I had some success with a new environment, but it eventually produced the same behavior. Now I’ve tried
spyder --resetand it seems to work, hopefully for good. Thanks for the tip!None of the updates (ipython, qtconsole, Spyder, Spyder dependencies) make a difference. But
spyder --resetseems to have done the trick. Which is odd, as this was a fresh environment. But thanks!This, solved my problem. I returned the plotted graphics to in line format
I have been having this same problem- but it only happens when I’m using an automatic graphics backend, for interacting with graphs. inline plotting doesn’t give me this issue spyder --reset reverts it to inline plotting, but it isn’t really a fix?
Could you try to update
IPythonandQtConsole? Maybe looking our Basic First Aid Guide could give more alternatives to try. Sorry to not be so helpful (there is not much we can do in this sort of installation issues for now 😕 ).Hi, could you guys check if updating
ipykernelto 5.3.4 helps?