After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 165817 - gobject.MainLoop needs to have a timeout to call PyErr_CheckSignals() like the gtk main loop
gobject.MainLoop needs to have a timeout to call PyErr_CheckSignals() like th...
Status: RESOLVED DUPLICATE of bug 154779
Product: pygobject
Classification: Bindings
Component: gobject
2.9.0
Other Linux
: Normal normal
: ---
Assigned To: Nobody's working on this now (help wanted and appreciated)
Python bindings maintainers
Depends on:
Blocks:
 
 
Reported: 2005-01-31 15:09 UTC by Mark McLoughlin
Modified: 2006-01-09 14:12 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
patch (1.39 KB, patch)
2005-01-31 15:10 UTC, Mark McLoughlin 		none Details | Review

Description Mark McLoughlin 2005-01-31 15:09:25 UTC 
In bug #72333 a timeout was added to the gtk main loop to call
PyErr_CheckSignals() so that signals get processed while we're in the main loop.

We need the same thing for gobject.MainLoop too. Attaching a patch which just
copies what jdahlin did.
Comment 1 Mark McLoughlin 2005-01-31 15:10:29 UTC 
Created attachment 36764 [details] [review]
patch
Comment 2 Mark McLoughlin 2005-01-31 15:21:09 UTC 
Also see:

http://www.daa.com.au/pipermail/pygtk/2004-April/007483.html
Comment 3 Gustavo Carneiro 2005-01-31 22:21:57 UTC 
This is practically (but not entirely) a dup of bug 154779.  As I say in that
bug report, I think timeouts are evil.

Do you really need to catch all signals, or just a few?
Comment 4 Mark McLoughlin 2005-02-01 09:27:01 UTC 

*** This bug has been marked as a duplicate of 154779 ***