Re: [pygtk] pygtk and threads.

[Dave Aitel]

Honestly, you save yourself days of debugging if you stick to a "GUI 
thread" and have all real work done in other threads. This requires a 
GUI Thread "queue" that you have it clean when it gets a chance. This is 
how CANVAS works, and we work on anything from *BSD to Windows this way. :>

Just my opinion, but if you find yourself doing a lot of 
thread_enter()/thread_leave(), you're guaranteed to introduce thousands 
of tiny annoying deadlocks.

-dave
Antoon Pardon wrote:
On Fri, Jan 21, 2005 at 08:28:58AM -0500, Chris Lambacher wrote:
 

Hi,
Threading does not work quite like that.  You don't have to call
threads enter and threads leave before every funtion call, only when
you are making pygtk calls from another thread.
   

I didn't write you had to put every function call between
threads_enter and threads_leave calls. But signal handlers
are automatically invoked that way and that IMO often is a
nuissance..
 

You would generally have:
if __name__ == '__main__':
   gtk.gdk.threads_init()
   gtk.gdk.threads_enter()
   gtk.main()
   gtk.gdk.threads_leave()
   

Are you sure? I see no need for the gtk.gdk.threads_enter()
and gtk.gdk.threads_leave() here. Or is this specific for
windows?
 

_______________________________________________
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/