rdcapx
March 5, 2022, 1:21am
1
Spyder 5.1.5 in anaconda… suddenly unable to run debug. Console locks up when debug is started on any script. scripts run perfectly in spyder if not debugging. If I install spyder 5.2.2 outside of anaconda, debug runs perfectly.
1 Like
I have the same Spyder problem as what you said.
Yes, I totally uninstalled Anaconda and the associated directory, spyder-py3; anaconda; and any directory under your User name that was associated with anaconda.
1 Like
I found an issue on Github talking about this problem recently:
opened 09:21PM - 15 Feb 22 UTC
closed 11:42PM - 16 Feb 22 UTC
status:Awaiting Followup
Hello,
First thanks for the excellent work of the contributors!
Anaconda3-20… 21.11-Windows-x86_64.exe
Windows 10
In the context of specific development, after reinstallation of anaconda, I am facing a problem with `spyder `that I reproduce here in a simpler situation.
I have installed `anaconda `from `Anaconda3-2021.11-Windows-x86_64.exe` on Windows 10.
The base environment has `spyder 5.1.5` installed.
I have written a few line script importing `numpy `(1.20.3) and `matplotlib `(3.4.3), with a breakpoint (at "x=").
```
import numpy as np
import matplotlib.pyplot as plt
if __name__ == '__main__':
x=np.linspace(1,10,10)
plt.hist(x**2)
```
The script runs, debugging works fine. Same after `conda update --all.`
I create an environment either from the Navigator or by hand from a conda shell (`conda env create –n test_from_shell`, that then appears in the Navigator).
In both created environments I install `spyder `(`conda install spyder`, and `spyder 5.1.5 `gets installed, like in the base), `numpy `(1.21.5) and `matplotlib `(3.5.0), not the same version.
`spyder-kernels` version is 2.1.3 in all cases, `ipykernel `versions are the same.
In the created environment the script runs correctly, **but the debugging does not work**, i.e. it starts, does not stop at nor reach the breakpoint and cannot be interrupted.
The symptoms are the same as in issue [#17314,](https://github.com/spyder-ide/spyder/issues/17314) and the steps are similar to the ones described in the attached pdf of that issue ([C__Users_jandre_Desktop_Problem_20220208_1900.pdf](https://github.com/spyder-ide/spyder/files/8026710/C__Users_jandre_Desktop_Problem_20220208_1900.pdf)
I have cloned the base environment through a yaml file and I have checked that in the cloned environment the script and the debugging run fine.
1. What is/are the guilty module(s) in the test environments leading to the debugger bug ? How can I find it ? How can this be solved?
2. Could you explain what are the default scripts installed when a new environment is created and why it is not the ones found in the base environment ? Is that expected ?
Thanks a lot
This may be helpful to you