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-September/136117.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
Mon Sep 1 07:30:27 CEST 2014
"R. David Murray" <rdmurray at bitdance.com>:

> PS: I recently switched from using selectors to using a timeout on a
> socket because in that particular application I could, and because
> reading a socket with a timeout handles EINTR (in recent python
> versions), whereas reading a non-blocking socket doesn't. Under the
> hood, a socket with a timeout is a non-blocking socket.

Under what circumstances would a nonblocking socket generate an EINTR?

I believe the biggest EINTR problem child is file I/O, which is always
blocking in linux.


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