These are chat archives for spyder-ide/public
@zloveslou_twitter Okay, we'll need a lot more details in order to be able to provide you useful help.
Did anything change between today and yesterday? Did you install, update, modify or remove any packages from your installation? Did you change any Spyder settings? Are you using a different environment? Is your code any different?
What code are you trying to run? What is the full, exact text of the error message? Does it occur when you launch Spyder, when you run your code, or some other time? What version of Spyder, Python, your OS, spyder-kernels, ipython, ipykernel, and Qtconsole are you using (you can get this information from the Help > About dialog and the Help > Depedencies dialog)? How did you install Spyder (e.g. Anaconda?
(including from Anaconda Navigator, Anaconda prompt, or by running "start.py" from anaconda prompt)
Did you also try the more standard methods of running the Spyder start menu shortcut or
spyder from the Anaconda prompt?
conda update spyder,
conda update conda, and
conda update pyqt(which one Google result suggested).
conda update spyder. I'll do that again now, though.
conda install spyder=3.3.3should get you the latest version.
set SPYDER_DEBUG=3, and then run Spyder with
spyder. Let us know any output you see.
set SPYDER_DEBUG=3and launching spyder...
I had a functioning Anaconda install, with two environments (for neuroscience tolboxes CaImAn and DeepLabCut). I was running Spyder from my caiman environment.
I was editing and running a script section-by-section (cell-by-cell? I am used to MatLab). The .py file for that script was located on another computer (I am wondering if this is related, in particular). This script included some parallelized elements, so there were multiple
wpython.exe daughter processes.
One section of the script was in the middle of running and I wanted it to stop. The "STOP" button wasn't working so I used the task manager to manually kill all the python.exe/wpython.exe processes I could see.
Next time I tried to start Spyder, this happened.
conda list qt
conda list qtand I see:
# packages in environment at C:\ProgramData\Anaconda3: # # Name Version Build Channel pyqt 5.9.2 py37h6538335_2 qt 5.9.7 vc14h73c81de_0 [vc14] qtawesome 0.5.3 py37_0 qtconsole 4.4.3 py37_0 qtpy 1.5.2 py37_0
spyder --reset. Other than that, I think the problem is actually with Qt/PyQt, not Spyder, since Spyder is pure Python, and thus can't actually crash Python by itself.
conda list outout
You can quote my post to see it
conda update conda conda create -n spyder-env spyder=3.3.3 conda activate spyder-env spyder
spyder --resetI just got "python has stopped working"
spyder-env, tried to run spyder, got "python has stopped working" again.
conda install pyqt=5.6and see if you get the same result. If that doesn't fix it, I'm not sure what will.
conda update spyder spyder-kernelswhenever a new release is released.
conda install qt=5.6
conda install qt=5.9.6before that. Was that correct, or was that supposed to be
nbconvert >=4.0: None (NOK)
SPYDER_DEBUGto to get it to stop outputting all this stuff? 0? 1?
You shouldn't need to. All you need to do is re-update Qt/PyQt with
conda install pyqt=5.9 and see if the problem re-occurs. If it does, revert with
conda install pyqt=5.6.
conda install pyqt=5.6in my other environments is likely to mess things up, and I should NOT try it as a workaround?
Are you saying that this Spyder instance can open IPython sessions in other environments and run code in those environments, as though I had run Spyder in those other environments to begin with?
Yep. All you need is Spyder-Kernels installed in those environments, and it should work just as if you started Spyder from there. You can run as many different Consoles in different environments as you want simultaneously in the same session. Read our guide to working with packages and envronments with Spyder for more.
Ah. OK. I think I get it now.
Yeah, its basically Spyder talks to QtPy, which talks to PyQt, which talks to Qt, which draws the Spyder interface on the screen.
Well, thank you very much for being so helpful and responsive.
Funny thing, I myself was on the line most of this time with a customer service rep trying to get a technical problem of my own resolved, lol.