python.exe shuts down as soon as I try to start an iPython console

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Anytime I start an iPython console from Spyder. It will start as a 
standalone, though.
2.
3.

What is the expected output? What do you see instead?
Nothing. Python.exe shuts down after a windows message that python.exe has 
stopped working, then spyder shuts down.

What version of the product are you using? On what operating system?
Windows 7, WinPython-64bit-3.3.2.2\python-3.3.2.amd64

Please provide any additional information below.

Original issue reported on code.google.com by cybervig...@gmail.com on 18 Aug 2013 at 11:14

[GoogleCodeExporter]

This bug may be related to the following post on Spyder's discussion group:
https://groups.google.com/forum/#!topic/spyderlib/E4uKC3SQ3iU

As I wrote on this thread, "considering the fact that there is no traceback 
(hard crash), the only way to find out where this comes from is to run Spyder 
from source checkout and update to older revisions until the bug disappears (or 
the opposite: update to the 2.3.0dev3 revision if it's working and update to 
newer revisions until the bug shows up).
If you need assistance, please do not hesitate to ask."

Original comment by pierre.raybaut on 19 Aug 2013 at 8:29

• Changed state: Accepted
• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

After some thinking, I might have a solution to show a traceback for this crash.

Just modify the code of spyderlib\widgets\internalshell.py in your WinPython 
installation and replace DEBUG by True at line 168:
http://code.google.com/p/spyderlib/source/browse/spyderlib/widgets/internalshell
.py#168

This should enable the DEBUG mode only for the internal shell which could be 
sufficient here.

Original comment by pierre.raybaut on 19 Aug 2013 at 4:28

[GoogleCodeExporter]

I tried that. No crash data, just the usual Windows "Python stopped working" 
message.

Original comment by cybervig...@gmail.com on 20 Aug 2013 at 1:24

[GoogleCodeExporter]

Hello, 

With the new version 3.3.2.3 of today, I triggered the problem once, and now I 
fail to reproduce it. It looks stable now.

Thanks a lot

Original comment by stonebi...@gmail.com on 22 Aug 2013 at 6:01

[GoogleCodeExporter]

Original comment by pierre.raybaut on 22 Aug 2013 at 6:37

• Changed state: Fixed

[GoogleCodeExporter]

Thanks, I'll download and try that. Although it's odd to trigger the problem 
once, and never again. It's the one white crow ;')

Original comment by cybervig...@gmail.com on 22 Aug 2013 at 7:22