This message bounced because the sender is not on the list, or they used a
different address to the one they subscribed with.
In answer to the question, the C interface does not grab the GTK lock when
entering an IO callback, so the python one does not either. Maybe it
should though -- I don't know. It probably doesnot call
threads_enter/leave for you because the IO callback interface is
implemented at the glib/gdk level.
It is probably correct to call threads_enter and threads_leave in your
callback. The calls will not do anything if pygtk was not compiled with
thread support.
If you think the current gtk behaviour is broken with respect to IO
callbacks, I recommend you take it up with the GTK developers.
James.
--
Email: [EMAIL PROTECTED]
WWW: http://www.daa.com.au/~james/
On Tue, 31 Aug 1999 [EMAIL PROTECTED] wrote:
> Subject: threads_enter/leave required in a non-threading program
> From: Andreas Degert <[EMAIL PROTECTED]>
>
> Hello,
>
> I'm using input_add() in a pygtk program to read from a socket. Both
> gtk and python are compiled with threads (debian), but my program
> doesn't use threads.
>
> When input is available on the socket, the supplied callback-function
> is called. If this function tries to display a non-modal window, the
> program locks up. The cure is to use threads_enter/leave in that
> function.
>
> Is this expected behaviour?
>
> cheers
> Andreas
>
To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
