Message200599
> 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. |
|
Date |
User |
Action |
Args |
2013-10-20 17:37:10 | sbt | set | recipients:
+ sbt, gvanrossum, db3l, ncoghlan, pitrou, larry, skrah, neologix, python-dev, David.Edelsohn |
2013-10-20 17:37:10 | sbt | set | messageid: <1382290630.75.0.873899733542.issue19293@psf.upfronthosting.co.za> |
2013-10-20 17:37:10 | sbt | link | issue19293 messages |
2013-10-20 17:37:10 | sbt | create | |
|