On 10/01/2010 09:40 AM, Friedrich Romstedt wrote: > There were several question on the user's list in the recent past > reporting hangs and similar when using TkAgg backend& interactive > mode. > > It is known that Tkinter doesn't play well with threading, as long as > one isn't done very carefully. > > It could be that matplotlib has implemented it in a way not safe for > Tkinter. This applies if there are Tkinter methods called from > threads other than those which imported Tkinter. > > It results in unpredicatable behaviour with exactly the features > reported: Hang-ups, blankening, partial hangup of part of the threads. > > Is a rewrite of the Tk interactive code necessary?
I don't see any use of the threading module in backend_tkagg.py or backend_bases.py. Is that what you are referring to? Ipython -pylab does use threads (version 0.10), but is intended to avoid problems by running all user code in a single separate thread. Eric > > Friedrich ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
