This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

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 <>
> 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:10sbtsetrecipients: + sbt, gvanrossum, db3l, ncoghlan, pitrou, larry, skrah, neologix, python-dev, David.Edelsohn
2013-10-20 17:37:10sbtsetmessageid: <>
2013-10-20 17:37:10sbtlinkissue19293 messages
2013-10-20 17:37:10sbtcreate