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/136092.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 EINTRMarko Rauhamaa marko at pacujo.net
Sun Aug 31 23:19:15 CEST 2014
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.

> Can you please elaborate? What do you mean by "get wrong"?

Proper handling of signals is difficult and at times even impossible.
For example it is impossible to wake up reliably from the select(2)
system call when a signal is generated (which is why linux now has
pselect).


Marko
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