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 348937 - 100ms timeouts in pygtk
100ms timeouts in pygtk
Status: RESOLVED FIXED
Product: pygobject
Classification: Bindings
Component: general
2.8.0
Other Linux
: Normal normal
: ---
Assigned To: Gustavo Carneiro
Python bindings maintainers
Depends on:
Blocks:
 
 
Reported: 2006-07-27 14:45 UTC by Yann Leboulanger
Modified: 2006-09-29 19:11 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
patch, based on markmc's pygobject mainloop code (3.34 KB, patch)
2006-07-27 16:12 UTC, Gustavo Carneiro 		none Details | Review

Description Yann Leboulanger 2006-07-27 14:45:07 UTC 
all pygtk applications wakes up every 100ms because of a timeout in pygtk.

[16:35:03] gjc: it was already solved once for gobject.MainLoop.run()
[16:35:19] gjc: we just need to copy the strategy to other main loops
Comment 1 Gustavo Carneiro 2006-07-27 16:12:07 UTC 
Created attachment 69744 [details] [review]
patch, based on markmc's pygobject mainloop code
Comment 2 Gustavo Carneiro 2006-07-27 16:24:32 UTC 
This only fixes the timeout for POSIX systems; win32 will have to keep using the timer...
Comment 3 John Ehresman 2006-07-27 16:58:59 UTC 
Hmm, I wonder if on win32 this is even needed.  Signals don't really exist on win32 (at least in the form they do on unix-like systems), but I'd need to look at how the keyboard interrupt exception is generated to say for sure