Aaron Optimizer Digulla <[EMAIL PROTECTED]> writes:
> Quoting Hrvoje Niksic <[EMAIL PROTECTED]>:
>
> > > > > (does it have anything to do with the threading code?).
> > > > I don't think so, no.
> > > Yes, that's the same. Threading doesn't work with the current
> > > implementation of Gtk because all Python threads are dead as long as
> > > Gtk waits in its mainloop for events (no Python code is executed ->
> > > Python can't switch the threads).
> > This is brain-dead on the part of Python, but that's another matter.
> > :-(
>
> No, actually it´s braindead of Gtk
Python threads have the requirement that you always have access to the
interpreter, because one thread appears to lock all the others while
running. This is abominable, and is a direct result of the
interpreter being non-thread-safe.
Gtk has the requirement that all Gtk actions are done in the same
thread, or that you implement semaphores on all Gtk entry-points.
This is abominable, and is a direct result of Gtk being
non-thread-safe.
So IMO they're both brain-dead and there's little we can do about it.
This is why I chose the SIGCHLD approach which also has its drawbacks,
but appears to work in practice.
To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
