[Python-Dev] RFC: PEP 475, Retry system calls failing with EINTR (original) (raw)
Ethan Furman ethan at stoneleaf.us
Sun Aug 31 23:38:04 CEST 2014
- Previous message: [Python-Dev] RFC: PEP 475, Retry system calls failing with EINTR
- Next message: [Python-Dev] RFC: PEP 475, Retry system calls failing with EINTR
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 08/31/2014 02:19 PM, Marko Rauhamaa wrote:
Victor Stinner <victor.stinner at gmail.com>:
Sorry but I don't understand your remark. What is your problem with retrying syscall on EINTR? The application will often want the EINTR return (exception) instead of having the function resume on its own.
Examples?
As an ignorant person in this area, I do not know why I would ever want to have EINTR raised instead just getting the results of, say, my read() call.
--
Ethan
- Previous message: [Python-Dev] RFC: PEP 475, Retry system calls failing with EINTR
- Next message: [Python-Dev] RFC: PEP 475, Retry system calls failing with EINTR
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]