On Mon, Jul 12, 1999 at 03:54:53PM -0400, Matt Wilson wrote:
> We've come up with a patch that solves the python global lock/gdk lock
> interation problem - but I have no idea if it is at all safe.
>
...
>
> static PyObject *_wrap_gdk_threads_leave(PyObject *self, PyObject *args) {
> if (!PyArg_ParseTuple(args, ":gdk_threads_leave"))
> return NULL;
> + Py_BEGIN_ALLOW_THREADS
Nah, we don't really need this here. We do need to go around and
look for any blocking functions and allow python threads there.
Synchronous X calls such as gtk_widget_show_now and gdk_flush should
definitely allow python threads as they could block indefinitely
if another program has a lock on the X server.
Back to hacking python code instead of debugging threading deadlocks.
:)
Matt
To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
