> I will have a look at the code for both PyGTK and OS X.
> Hopefully that will show me more of the best way of
> handling this.
The code in PyGTK is a bit easier to understand than the code for OS X. The OS
X code also includes stuff to handle SIGINTs (keyboard interrupts by ctrl-c),
which is
ld
> be a lot easier if Python itself supported event loops.
Yes, that would be nice!!!
Cheers,
Brian
> --Michiel
>
> --- On Sun, 2/8/09, Brian Granger wrote:
>
>> From: Brian Granger
>> Subject: [matplotlib-devel] Interactive wx/pylab with no threads
>> (P
; Subject: [matplotlib-devel] Interactive wx/pylab with no threads
> (PyOS_InputHook)
> To: matplotlib-devel@lists.sourceforge.net, "IPython Development list"
>
> Date: Sunday, February 8, 2009, 7:08 PM
> IPython and matplotlib devs,
>
> Over the weekend I have bee
On Sun, Feb 08, 2009 at 04:08:31PM -0800, Brian Granger wrote:
> * In the current matplotlib backend wx.Yield() is called in a way that
> is not safe as far as protecting against recursive calls to Yield. I
> think it should be called in this way:
> app = wx.GetApp()
> if app is not None:
> app
IPython and matplotlib devs,
Over the weekend I have been playing around to see if it is possible
to do interactive GUI work with wx from IPython *without using
threads*. The idea here is to use PyOS_InputHook. Currently, recent
versions of PyQt4 and PyGTK do this and if we can get wx working, w
