STINNER Victor added the comment: Nathaniel Smith added the comment: > In any case, the issue here remains that one shouldn't have to use > set_wakeup_fd for a signal to interrupt time.sleep etc.
CPython implements a C signal handler which sets a flag and then exits immediately. The thread getting the signal will probably interrupts the current blocking syscall with EINTR. CPython detects that a signal flag was set, calls the *Python* signal handler. If the Python signal handler raises an exception, the syscall is abandonned. Otherwise, the syscall is restarted. So "interrupting sleep" is only reliable if: * there is only one thread (the "main" thread) * the syscall is interrupted with EINTR * the signal handler raises an exception When you implement an event loop, raising an exception may be the best design. In asyncio, the Python signal handler calls loop.call_soon() to execute the final callback (3rd signal handler of the same signal!). The rule in asynico is not call blocking syscalls, or at least ensure that they don't block too long (ex: use aiofiles to access the filesystem). ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue21895> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
