On Thu, 7 Feb 2002, Brian Craft wrote:
> errrrr..... Does orbit-python also hammer the python main loop? After orb.run()
> everything comes to a halt -- threads don't run, timers don't execute.
Python's global interpreter lock works that way: orb.run() is atomic, and
signals aren't handled, etc. IIRC it's been said that the GTK mainloop
uses a set of hacks to get things working, but I may be wrong. Tack is an
authority on this, and if you search the ML archives, you'll see me asking
the same questions.
Take care,
--
Christian Reis, Senior Engineer, Async Open Source, Brazil.
http://async.com.br/~kiko/ | [+55 16] 272 3330 | NMFL
|