Mon Mar 19 11:03:08 CDT 2007
Walter Dörwald wrote:
> Fernando Perez wrote:
>> On 3/12/07, Nikolas Tautenhahn <firstname.lastname@example.org> wrote:
>>> Hi there,
>>> Walter Dörwald wrote:
>>>>>>> ipython -wthread
>>>>>>> but got all kinds of error messages. It would be great if it could
>>>>>>> work there, since then people could pop igrid browsers while retaining
>>>>>>> normal control of their shell, much like matplotlib (with the WX
>>>>>>> backend) or the Enthought tools work.
>>>>> I don't see any problems here with -wthread (except that the next input
>>>>> prompt doesn't start on the next line). This is with wx 2.8/Python
>>>>> on Windows.
>>>>> Can you post what error messages you got?
>> Here's what I see:
>> wx._core.PyNoAppError Traceback (most
>> recent call last)
>> in GetAttr(self, *args)
>> 133 def GetAttr(self, *args):
>> 134 attr = wx.grid.GridCellAttr()
>> --> 135 attr.SetFont(wx.Font(self.fontsize, wx.TELETYPE,
>> wx.NORMAL, wx.NORMAL))
>> 136 return attr
>> /usr/lib/python2.4/site-packages/wx-2.6-gtk2-unicode/wx/_gdi.py in
>> __init__(self, *args, **kwargs)
>> 1720 """
>> 1721 if kwargs.has_key('faceName'): kwargs['face'] =
>> kwargs['faceName'];del kwargs['faceName']
>> -> 1722 newobj = _gdi_.new_Font(*args, **kwargs)
>> 1723 self.this = newobj.this
>> 1724 self.thisown = 1
>> PyNoAppError: The wx.App object must be created first!
>> This message gets printed zillions of times, since it seems to be
>> triggered by an event handler on mouse movement. So basically the
>> screen goes nuts printing this same traceback over and over as fast as
>> it can.
> OK, this seems to be wx related. I'll downgrade my wx on Windows to 2.6
> and we'll see what happens.
OK, with wx 2.6 I can reproduce the problem.
Can you try r2161? For me this delays the problem until you open
multiple igrid browser and close one of them.
One solution might be to only allow one igrid browser. The other would
probably be that all igrid browsers are frames in only one wx application.
More information about the IPython-dev