Spyder 3.2.6 [crashes/won't launch] after conda install into a fresh Python 2.7 environment

Hi everyone,

Description of your problem

Thanks for looking into it. The following error notification pop up when I launch spyder 3.2.6.

I did some search on Internet and tried the following stuffs and still cannot solve the problem. ‘spyder --reset’ and then do spyder, this seems loading stuffs without showing anything. However, a new pythonw.exe runs at the background though I don’t where it is.

spyder --show-console shows same situation above.

delete the .spyder/spyder.lock folder delete the .spyder2 folder both shows same error notification.

What steps will reproduce the problem? Initially, I got the error notification above. install spyder in a brand-new virtual environment of python2.7 created via conda

Versions and main components

• Spyder Version: 3.2.6
• Python Version: python 2.7.114
• Qt Version: 5.6.2
• PyQt Version: 5.6.0
• Operating system: windows 7, 64bits

[CAM-Gerlach]

Thanks for following up, and for trying several techniques and search your issue before posting here. I’m sorry, I guess I must have misinterpreted your post. Since you never actually directed stated in the body of it what your actual problem was, particularly not near the top where one generally does so, and the title started with

Still cannot solve

and your first line was

Thanks for looking into it.

coupled with the fact that you had just posted at least one other issue, hopefully you can see how this looked like a followup post to some other topic, not a self-contained bug report. Unfortunately, a number of users lately have been clogging up the system by doing the former and this one appeared to fit the pattern, but I’m sorry I jumped to conclusions so quickly before asking you to clarify. We just have very limited time and resources right now, being unfunded, and the constant barrage of duplicate issues we have to deal with saps a significant portion of what we do have.

To help avoid this in the future and ensure you get the best help possible, please make sure your title and the first few lines/paragraph(s) contains a detailed description of what the actual issue is, rather than a line or two referring to such buried at the very end. Furthermore, a title like

Still cannot solve spyder crash on python2.7 after a few attempts.

would make sense I suppose for a help forum, but isn’t very helpful for a bug tracker; instead, something like

Spyder 3.2.6 [crashes/won’t launch] after conda install into a fresh Python 2.7 environment

is much more appropriate and descriptive.

Anyway, that aside, my main recommendation to you is to diligently follow all the steps/procedures described in the Spyder Troubleshooting Guide, specifically the Basic First Aid and Emergency CPR sections, which resolve the great majority of Spyder installation issues.

If it still isn’t working, please post any additional information listed in relevant subsection as a comment on this thread, and we’ll see what we can do.

spyder --show-console shows same situation above.

This doesn’t do anything; it is already enabled by default and is thus deprecated. spyder --debug is what you want.

delete the .spyder/spyder.lock folder delete the .spyder2 folder

spyder --reset should already take care of the needed portion of this for you; hopefully this didn’t mess anything up.

Initially, I got the error notification above.

As the (I’d assume localized) text states, this just means Spyder crashed last time you were using it, not that anything’s necessarily wrong this session. The next version of Spyder will include an enhanced version of that dialog, with clearer and more detailed descriptive text, and links to more help resources including the troubleshooting guide. Hopefully that should solve any confusion there.

Anyway, if you’ve made it to the end of this mega-post, congrats. Your kitty (profile photo) is very cute, by the way…looks a lot like my precious cat.

[CAM-Gerlach]

As @ccordoba12 states in #5967 it is not possible (to our knowledge) to receive that error without a plugin installed, as no object called DummyDock exists anywhere in our codebase.

I don’t want to prolong this any further, but to explain why we’re a little frustrated, in my second post I specifically asked

Do you have any Spyder plugins installed, like Spyder-terminal, or any pip-installed or otherwise nonstandard packages in the environment?

and you replied with

For this fresh python 2.7 environment, I haven’t install any plugins or packages yet.

Also, spyder-autopep8 was directly mentioned as a potential source of issues, with uninstalling it being the solution, under “Plugin Problems” in the troubleshooting guide I repeatedly requested you read for the past three consecutive posts.