A RetroSearch Logo

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

Search Query:

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

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

[Python-Dev] RFC: PEP 475, Retry system calls failing with EINTR [Python-Dev] RFC: PEP 475, Retry system calls failing with EINTREthan Furman ethan at stoneleaf.us
Sun Aug 31 23:38:04 CEST 2014
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~
More information about the Python-Dev mailing list

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