No, it's the opposite. The PEP doesn't change the default behaviour of SIGINT: CTRL+C always interrupt the program. Victor Le 1 sept. 2014 08:12, "Paul Moore" <p.f.moore at gmail.com> a écrit : > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20140901/859789d9/attachment.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4