Victor Stinner victor.stinner at gmail.com
Sun Aug 31 22:59:16 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 ]

---

Hi,

Sorry but I don't understand your remark. What is your problem with
retrying syscall on EINTR? Can you please elaborate? What do you mean by
"get wrong"?

Victor

Le dimanche 31 août 2014, Marko Rauhamaa <marko at pacujo.net> a écrit :

> Victor Stinner <victor.stinner at gmail.com <javascript:;>>:
>
> > Proposition
> > ===========
> >
> > If a system call fails with ``EINTR``, Python must call signal
> > handlers: call ``PyErr_CheckSignals()``. If a signal handler raises
> > an exception, the Python function fails with the exception.
> > Otherwise, the system call is retried.  If the system call takes a
> > timeout parameter, the timeout is recomputed.
>
> Signals are tricky and easy to get wrong, to be sure, but I think it is
> dangerous for Python to unconditionally commandeer signal handling. If
> the proposition is accepted, there should be a way to opt out.
>
>
> Marko
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20140831/774bcbc4/attachment.html>

---

• 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 ]

---

More information about the Python-Dev mailing list