On 22.02.2010, at 16:18, Tobias Weber wrote: > This changes nothing when using X11, but on a Quartz build gtk.main_quit() no > longer exits the process, only SIGKILL does!
BTW this happened on both 10.5 with MacPorts and 10.6 with my own build I found another mention of the problem, and a proposed fix by commenting out close(real_source->fds[0]): http://sourceforge.net/mailarchive/forum.php?thread_name=4A48FA0E.3080100%40eversholt.net&forum_name=gramps-devel What do you think? It is confirmed by a process sample I took: 891 Thread_13713 DispatchQueue_1: com.apple.main-thread (serial) 891 start 891 Py_Main 891 PyRun_SimpleFileExFlags 891 PyRun_FileExFlags 891 Py_CompileString 891 PyEval_EvalCode 891 PyEval_EvalCodeEx 891 PyEval_EvalFrameEx 891 PyEval_EvalFrameEx 891 _wrap_gtk_main 891 g_source_destroy 891 g_source_destroy_internal 891 g_source_unref_internal 891 pygtk_main_watch_finalize 891 close$UNIX2003 891 Thread_13714 DispatchQueue_2: com.apple.libdispatch-manager (serial) 891 start_wqthread 891 _pthread_wqthread 891 _dispatch_worker_thread2 891 _dispatch_queue_invoke 891 _dispatch_mgr_invoke 891 kevent 891 Thread_13719 891 thread_start 891 _pthread_start 891 select_thread_func 891 g_poll 891 select$DARWIN_EXTSN I did not find anything on https://bugzilla.gnome.org/buglist.cgi?product=pygtk _______________________________________________ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://faq.pygtk.org/
