Toby D. Reeves wrote:
>Hello,
>
>I discovered the same "feature" on Redhat 7.2 last week. It turns out that
>pygtk is compiled as part of the gnome-python package. PyGtk IS compiled
>with threads enabled. BUT someone applied a broken patch that conditionally
>call's g_thread_init in init_pygtk(
arrange for g_thread_init to be called
> elsewhere before "import gtk".
>
>
> Toby
>
>
> - Original Message -
> From: "Ivo van der Wijk" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, December 10, 2001 3:31 PM
> Sub
OTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, December 10, 2001 3:31 PM
Subject: Re: [pygtk] Threading problem/question
> On Mon, Dec 10, 2001 at 11:01:32AM +0100, Ivo van der Wijk wrote:
> > Hi all,
> >
>
> Okay, I guess the redhat rpm doesn't have thread suppo
On Mon, Dec 10, 2001 at 11:01:32AM +0100, Ivo van der Wijk wrote:
> Hi all,
>
Okay, I guess the redhat rpm doesn't have thread support or so - I compiled
pygtk myself (against python2.1), which fixes all problems again.
Ivo
--
Drs. I.R. van der Wijk -=-
Br
Hi all,
I learned that when using threads with pygtk, calls to gtk should be
surrounded by threads_enter/threads_leave.
This has always worked fine for me, until I recently upgraded my linux
system to redhat 7.2, now I suddenly get 'async reply' xlib errors (which
you always get if you don't use
