From: Fernando P. <fpe...@gm...> - 2010-10-10 20:36:51
|
On Sun, Oct 10, 2010 at 12:49 PM, Friedrich Romstedt <fri...@gm...> wrote: > > Second, I would be very interested in more information about the > ipython -pylab threading. What do you mean with "running all user > code in a single separate thread"? When it's not the thread importing > Tkinter, the problem persists. > Two things to note: - ipython, even in the 0.10 series, uses threads for the Qt, Gtk and Wx backends, but *not* for Tk, because python automatically pumps the Tk event loop when the console blocks on reading (via the C API PyOSInputHook call). So there is exactly *zero* threading added by ipython in the specific case of a Tk backend. - in the 0.11 ipython series, we abandoned threading altogether (it's just too brittle) and moved to a model similar to the Tk one for *all* backends, we now use PyOSInputHook with all mpl backends. hth, f |