[issue22114] You cannot call communicate() safely after receiving an exception (EINTR or EAGAIN)
Amrith Kumar
report at bugs.python.org
Tue Aug 5 18:40:16 CEST 2014
Amrith Kumar added the comment:
The issue turned out to be something funky in monkey patching.
os.read() shouldn't be getting called if the monkey patch was correct in the first place.
----------
resolution: -> not a bug
status: open -> closed
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue22114>
_______________________________________
More information about the Python-bugs-list
mailing list