Yes I already use this, but I think the problem is that the other toolkits need the GIL to update but raw_input() also grabs the GIL so you cannot examine your plot in a pause (i.e. raw_input()). I think that TK is able to avoid this problem as a side effect of being in a "C thread" instead of a python thread which is a side effect of being part of the python distribution. I think.
Jon. On Mon, Mar 9, 2009 at 4:13 PM, Sandro Tosi <mo...@debian.org> wrote: > On Sun, Mar 8, 2009 at 21:03, Jonathan Taylor > <jonathan.tay...@utoronto.ca> wrote: >> Wow... changing to TkAgg backend makes raw_input() just work. I >> suppose this is because the Tk thread does not need the GIL to render? >> Is there a downside to using TkAgg? I am also noticing that it is >> much faster than GtkAgg. > > If you want different backends than tkagg (that plays nice with > interactive interpreters), you could try > > $ ipython -pylab > > that is able to identify the wanted backend and work correctly with it > while keeping the interactive prompt available. > > Cheers, > -- > Sandro Tosi (aka morph, morpheus, matrixhasu) > My website: http://matrixhasu.altervista.org/ > Me at Debian: http://wiki.debian.org/SandroTosi > ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
