Re: bugs regarding late g_thread_init() calls

On Ter, 2007-01-02 at 14:34 +0100, Tim Janik wrote:
> hey all.
> since the very early inception of the glib threading system, the docs
> say ( ):
>  	You must call g_thread_init() before executing any other GLib
>  	functions in a threaded GLib program.

  In PyGObject it is virtually impossible to guarantee that
g_thread_init() gets called before using some other GLib APIs.  At least
not without changing the API.  That's because g_thread_init() is called
by the python function gobject.threads_init(), but you obviously can't
call gobject.threads_init() without importing gobject first, and of
course "import gobject" already calls some GLib APIs...  This is a very
tricky problem :|

Gustavo J. A. M. Carneiro
<gjc inescporto pt> <gustavo users sourceforge net>
The universe is always one step beyond logic

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]