On Fri, Apr 01, 2005 at 12:52:21PM -0500, John Ehresman wrote: > Antoon Pardon wrote: > >>>However when I remove the gtk.threads_leave() and gtk.threads_enter() > >>>calls from my program after sometime the program crashes and I get the > >>>following message: > >>> > >>> Xlib: unexpected async reply (sequence 0x10e6b)! > >>> > >>>Now I'm wondering. Is this a bug in pygtk or is the documentation not > >>>accurate? I'm using python 2.3.5 and pygtk 2.6.1 on a Debian testing > >>>machine. > >> > >>Threads can be a pain in the ass. If you handling gui then you should > >>not remove threads_enter()/leave(). > > > > > >So, according to you this is a documentation problem? > > A couple of comments here: > > * If multiple threads call gtk/gdk functions are used, then > threads_enter()/leave() must be used. If the documentation suggests > otherwise, it's incorrect.
Well IMO the documentation does so for programs with only python threads: http://www.pygtk.org/pygtk2reference/gdk-functions.html#function-gdk--threads-init More specifically the third bullet. -- Antoon Pardon _______________________________________________ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
