[Python-Dev] Signals, threads, blocking C functions (original) (raw)
Adam Olsen rhamph at gmail.com
Tue Sep 5 05:41:13 CEST 2006
- Previous message: [Python-Dev] Signals, threads, blocking C functions
- Next message: [Python-Dev] Signals, threads, blocking C functions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 9/4/06, Gustavo Carneiro <gjcarneiro at gmail.com> wrote:
Now, we've had this API for a long time already (at least 2.5 years). I'm pretty sure it works well enough on most *nix systems. Event if it works 99% of the times, it's way better than failing 100% of the times, which is what happens now with Python.
Failing 99% of the time is as bad as failing 100% of the time, if your goal is to eliminate the short timeout on poll(). 1% is quite a lot, and it would probably have an annoying tendency to trigger repeatedly when the user does certain things (not reproducible by you of course).
That said, I do hope we can get 100%, or at least enough nines that we can increase the timeout significantly.
-- Adam Olsen, aka Rhamphoryncus
- Previous message: [Python-Dev] Signals, threads, blocking C functions
- Next message: [Python-Dev] Signals, threads, blocking C functions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]