Changes by STINNER Victor victor.stin...@gmail.com:
--
resolution: - duplicate
status: open - closed
superseder: - handle EINTR in the stdlib
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11266
STINNER Victor added the comment:
It was already discussed in other issues, the issue is not specific to
asyncore: Python code should not handle EINTR. IMO the C module socket should
handle EINTR for you.
--
nosy: +haypo
___
Python tracker
Марк Коренберг socketp...@gmail.com added the comment:
When using non-blocking IO, we issue select (or poll,epoll), and after that
kernel should guarantee, that recv or send will complete immediatelly,
transferring data as needed. But sometimes (as Linux is buggy), such operations
results in
Марк Коренберг socketp...@gmail.com added the comment:
http://unix.derkeiler.com/Mailing-Lists/FreeBSD/hackers/2008-02/msg00457.html
Okay, linux is not buggy :)))
EINTR may occur if SA_RESTART is not specified in sigaction.
--
___
Python tracker
Vetoshkin Nikita nikita.vetosh...@gmail.com added the comment:
Here's a similar bug: http://bugs.python.org/issue7978.
EINTR may occur if SA_RESTART is not specified in sigaction.
Some syscalls (like select) will generate EINTR despite SA_RESTART. man 7 signal
--
nosy: +nvetoshkin
Giampaolo Rodola' g.rod...@gmail.com added the comment:
Again, it's not clear to me what you are complaining about.
Please try to be more clear and/or provide a patch.
--
nosy: +giampaolo.rodola
___
Python tracker rep...@bugs.python.org
Changes by Florian Mayer florma...@aim.com:
--
nosy: +segfaulthunter
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11266
___
___
Python-bugs-list
New submission from Марк Коренберг socketp...@gmail.com:
in spite of usage of non-blocking IO, syscalls may return EINTR if signal
arrive during some syscalls.
It is desirable to re-call syscall after receiving EINTR. Trivial loops should
be implemented around (recv, send, connect, accept)
