[issue22114] You cannot call communicate() safely after receiving EAGAIN

[R. David Murray]

R. David Murray added the comment:

I believe our recent thinking in recent times has been to handle EAGAIN in the higher level interfaces such as subprocess, not expose them to the caller.  Does python3 have the same problem?

I isn't clear that you have provided enough information to reproduce this.  Any chance you could reproduce it without using eventlet?

----------
components: +Library (Lib) -IO
nosy: +gps, r.david.murray
stage:  -> needs patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue22114>
_______________________________________