Message200599
| Author |
sbt |
| Recipients |
David.Edelsohn, db3l, gvanrossum, larry, ncoghlan, neologix, pitrou, python-dev, sbt, skrah |
| Date |
2013年10月20日.17:37:10 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1382290630.75.0.873899733542.issue19293@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> I guess we'll have to write platform-dependent code and make this an
> optional feature. (Essentially, on platforms like AIX, for a
> write-pipe, connection_lost() won't be called unless you try to write
> some more bytes to it.)
If we are not capturing stdout/stderr then we could "leak" the write end of a pipe to the child. When the read end becomes readable we can call the process protocol's connection_lost().
Or we could just call connection_lost() when reaping the pid. |
|