RetroSearch Browse

Mon Sep 1 08:12:06 CEST 2014 · https://mail.python.org/pipermail/python-dev/2014-September/136120.html

On 31 August 2014 22:38, Victor Stinner <victor.stinner at gmail.com> wrote:
> This case is described as the use case #2 in the PEP, so it is supported. As
> written in the PEP, if you want to be notified of the signal, set a signal
> handler which raises an exception. For example the default signal handler
> for SIGINT raises KeyboardInterrupt.

Wait - sigint? Does this mean that (unless the application adds a
signal handler) keyboard interrupts will be in effect ignored while in
a system call? I'm not sure I like that - I'd rather Ctrl-C always
interrupted the program. Specifically, in one-off scripts that *don't*
take care to handle all errors appropriately and just show the
traceback...

Paul

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2014-September/136120.html below:

[Python-Dev] RFC: PEP 475, Retry system calls failing with EINTR