You're right, being able to reproduce the bug is a good thing but in that
case, the bug is not 100% reproducible. Sometimes it crashes, sometimes
not. And I don't understand why.
Anyway, I was able to find a way to prevent the application from crashing
when an IPython console is opened by commenting out lines 354-376 in
IPython\qt\console\console_widget.py:
self.increase_font_size = QtGui.QAction("Bigger Font",
self,
shortcut=QtGui.QKeySequence.ZoomIn,
shortcutContext=QtCore.Qt.WidgetWithChildrenShortcut,
statusTip="Increase the font size by one point",
triggered=self._increase_font_size)
self.addAction(self.increase_font_size)
self.decrease_font_size = QtGui.QAction("Smaller Font",
self,
shortcut=QtGui.QKeySequence.ZoomOut,
shortcutContext=QtCore.Qt.WidgetWithChildrenShortcut,
statusTip="Decrease the font size by one point",
triggered=self._decrease_font_size)
self.addAction(self.decrease_font_size)
self.reset_font_size = QtGui.QAction("Normal Font",
self,
shortcut="Ctrl+0",
shortcutContext=QtCore.Qt.WidgetWithChildrenShortcut,
statusTip="Restore the Normal font size",
triggered=self.reset_font)
self.addAction(self.reset_font_size)
Could you please try and comment those lines on your side to see if it has
the same effect?
-Pierre
2013/8/19 <[email protected]>
> I would rather consider a perfectly reproducible bug very good news.
> Wouldn't it be possible to escaladate the bug to ipython team ?
>
> They are already doing a change in "qt.console.rich_ipython_widget",
> related to old "qt console" / "py3k" bugs.
> (https://github.com/ipython/ipython/pull/4054/files)
>
>
> Le lundi 19 août 2013 19:22:14 UTC+2, Pierre Raybaut a écrit :
>>
>> I'm now able to reproduce this issue with a WinPython 3.3.2.2
>> distribution installed on a fresh Win7 Pro 64bit VM.
>>
>> So far my conclusion is that python.exe crashes when calling
>> IPythonWidget's contructor (when object is instantiated) which is not good
>> news as this widget is from IPython.qt.console.rich_**ipython_widget. In
>> other words, I'm not close to a solution...
>>
>> Have you tried upgrading Spyder to 2.3.0dev5 in your "old" WinPython 3.3
>> install? (the one that works)
>>
>> -Pierre
>>
>>
>> 2013/8/19 big stone <[email protected]>
>>
>>> Hello Pierre,
>>>
>>> I just tried and it changed nothing, (and the debug vs 2010 asked me a
>>> service pack, that I'm currently installing).
>>> But first :
>>> - I had 2 success, by starting a ipython qt console, then closing spyder
>>> (and not the ipython console)
>>> - then it failed when I , if I did note well the chain of events, when I
>>> :
>>> * started again a ipython qt console,
>>> * then closed the ipython qt console but not spyder,
>>> * then retried
>>> ==> May it be a 'wrong' chain of actions that you didn't anticipate
>>> users could do ?
>>> ==> is there a magic spyder --reset or something like that that I should
>>> do or look ?
>>>
>>>
>>>
>>>
>>> 2013/8/19 Pierre Raybaut <[email protected]>
>>>
>>>> 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<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.
>>>>
>>>> -Pierre
>>>>
>>>> Le lundi 19 août 2013 10:27:38 UTC+2, Pierre Raybaut a écrit :
>>>>
>>>>> Unfortunately, I can't reproduce this bug.
>>>>>
>>>>> So, 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.
>>>>>
>>>>> This may also be related to this bug report:
>>>>> http://code.google.com/p/**winpy**thon/issues/detail?id=77<http://code.google.com/p/winpython/issues/detail?id=77>
>>>>>
>>>>> -Pierre
>>>>>
>>>>> Le samedi 17 août 2013 03:12:10 UTC+2, Jim Passmore a écrit :
>>>>>
>>>>>> Confirming similar problem running dev5, in a freshly unzipped 32-bit
>>>>>> WinPython 3.3.2.2, on 32-bit Win7.
>>>>>>
>>>>>>
>>>>>> On Monday, August 12, 2013 12:10:28 PM UTC-4, [email protected]:
>>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> I'm experimenting on windows vista 32bit the new spyder 2.3.0.dev5
>>>>>>> (as a non-manager of my pc).
>>>>>>> (via winpython 3.3.2.2, so python3.3).
>>>>>>>
>>>>>>> Spyder fails to launch reliabily an IPython (1.0.0) console.
>>>>>>> Procedure =
>>>>>>> - click on "Interpreters-> open an IPython Console",
>>>>>>> - I get an opening IPython console the trick about the way to
>>>>>>> connect to an existing IPython Kernel,
>>>>>>> - then after about 5 seconds python.exe stops with a debug message
>>>>>>> : "Exception non gérée à 0x00000000 dans python.exe : 0xC0000005:
>>>>>>> Access
>>>>>>> violation."
>>>>>>>
>>>>>>>
>>>>>>> Does anyone experience the same unfortunate problem ?
>>>>>>>
>>>>>>>
>>>>>>> Nota :
>>>>>>> - among the fails, I had two success,
>>>>>>> - a "python.exe" process remains in the background (and seems to be
>>>>>>> the launched ipython kernel)
>>>>>>> - I tried with mathjax installed, without more success,
>>>>>>> - I removed Pylab activation when opening IPython console, no more
>>>>>>> success,
>>>>>>> - on the exact same PC, I have not problems with previous spyder
>>>>>>> (2.3.0.dev3) and python1.0.0, except a kind remindermessage
>>>>>>> "The top-level `frontend` package has been deprecated. "
>>>>>>>
>>>>>>> --
>>>> You received this message because you are subscribed to a topic in the
>>>> Google Groups "spyder" group.
>>>> To unsubscribe from this topic, visit https://groups.google.com/d/**
>>>> topic/spyderlib/E4uKC3SQ3iU/**unsubscribe<https://groups.google.com/d/topic/spyderlib/E4uKC3SQ3iU/unsubscribe>
>>>> .
>>>> To unsubscribe from this group and all its topics, send an email to
>>>> spyderlib+...@**googlegroups.com.
>>>> To post to this group, send email to [email protected].
>>>>
>>>> Visit this group at
>>>> http://groups.google.com/**group/spyderlib<http://groups.google.com/group/spyderlib>
>>>> .
>>>> For more options, visit
>>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out>
>>>> .
>>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "spyder" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to spyderlib+...@**googlegroups.com.
>>> To post to this group, send email to [email protected].
>>>
>>> Visit this group at
>>> http://groups.google.com/**group/spyderlib<http://groups.google.com/group/spyderlib>
>>> .
>>> For more options, visit
>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out>
>>> .
>>>
>>
>>
> --
> You received this message because you are subscribed to the Google Groups
> "spyder" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/spyderlib.
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
You received this message because you are subscribed to the Google Groups
"spyder" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/spyderlib.
For more options, visit https://groups.google.com/groups/opt_out.
