RetroSearch Browse

Mon Sep 1 12:40:29 CEST 2014 · https://mail.python.org/pipermail/python-dev/2014-September/136132.html

There's no return value, a KeywordInterrupt exception is raised.
The PEP wouldn't change this behavior.

As for the general behavior: all programming languages/platforms
handle EINTR transparently.
It's high time for Python to have a sensible behavior in this regard.

2014-09-01 8:38 GMT+01:00 Marko Rauhamaa <marko at pacujo.net>:
> Victor Stinner <victor.stinner at gmail.com>:
>
>> No, it's the opposite. The PEP doesn't change the default behaviour of
>> SIGINT: CTRL+C always interrupt the program.
>
> Which raises an interesting question: what happens to the os.read()
> return value if SIGINT is received?
>
>
> Marko
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: https://mail.python.org/mailman/options/python-dev/cf.natali%40gmail.com

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

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

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