[issue10963] "subprocess" can raise OSError (EPIPE) when communicating with short-lived processes

2016-02-17 Thread Martin Panter
Martin Panter added the comment: FTR Issue 26372 has been opened about Serhiy’s bug with stdin.close() raising EPIPE. -- nosy: +martin.panter ___ Python tracker

[issue10963] subprocess can raise OSError (EPIPE) when communicating with short-lived processes

2015-03-01 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: self.stdout.close() also can fail with EPIPE or EINVAL if the stream is buffered (text streams are buffered). I.e. communicate() in text mode can loss the data. See also issue21619. -- nosy: +serhiy.storchaka ___

[issue10963] subprocess can raise OSError (EPIPE) when communicating with short-lived processes

2011-04-05 Thread Roundup Robot
Roundup Robot devnull@devnull added the comment: New changeset c10d55c51d81 by Ross Lagerwall in branch '2.7': Issue #10963: Ensure that subprocess.communicate() never raises EPIPE. http://hg.python.org/cpython/rev/c10d55c51d81 New changeset 158495d49f58 by Ross Lagerwall in branch '3.1': Issue

[issue10963] subprocess can raise OSError (EPIPE) when communicating with short-lived processes

2011-04-05 Thread Ross Lagerwall
Ross Lagerwall rosslagerw...@gmail.com added the comment: Committed, thanks. -- assignee: - rosslagerwall resolution: - fixed stage: patch review - committed/rejected status: open - closed type: feature request - behavior ___ Python tracker

[issue10963] subprocess can raise OSError (EPIPE) when communicating with short-lived processes

2011-04-02 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: I think it's best to remove all this inconsistency and fix it so that EPIPE is never generated and then backport it to 2.7, 3.1, 3.2. Attached is a patch which fixes it for poll, select, windows and adds two tests. The patch looks good to

[issue10963] subprocess can raise OSError (EPIPE) when communicating with short-lived processes

2011-04-01 Thread Ross Lagerwall
Ross Lagerwall rosslagerw...@gmail.com added the comment: Marked #6457 as a duplicate. See #6457 for more discussion. -- nosy: +Yaniv.Aknin, amaury.forgeotdarc, dwalczak, mcrute ___ Python tracker rep...@bugs.python.org

[issue10963] subprocess can raise OSError (EPIPE) when communicating with short-lived processes

2011-03-31 Thread Ross Lagerwall
Ross Lagerwall rosslagerw...@gmail.com added the comment: I'd argue that this is not a feature request but a bug. I did some testing of this issue and the problem is that EPIPE is only generated sometimes depending on the time the process takes to finish, the size of the data sent, the

[issue10963] subprocess can raise OSError (EPIPE) when communicating with short-lived processes

2011-01-24 Thread Federico Simoncelli
Federico Simoncelli fsimo...@redhat.com added the comment: I agree they are orthogonal. The problem is that Popen.communicate doesn't support a way to ignore the exception and keep reading from stdout and sterr until the process dies. When the child closes the stdin its (error/debug/info)

[issue10963] subprocess can raise OSError (EPIPE) when communicating with short-lived processes

2011-01-24 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: You are right, this is suboptimal. It would also be a behaviour change from currently, but it seems beneficial. -- nosy: +gregory.p.smith type: - feature request ___ Python tracker

[issue10963] subprocess can raise OSError (EPIPE) when communicating with short-lived processes

2011-01-24 Thread Giampaolo Rodola'
Changes by Giampaolo Rodola' g.rod...@gmail.com: -- nosy: +giampaolo.rodola ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10963 ___ ___

[issue10963] subprocess can raise OSError (EPIPE) when communicating with short-lived processes

2011-01-20 Thread Dave Malcolm
New submission from Dave Malcolm dmalc...@redhat.com: If we start a short-lived process which finishes before we begin communicating with it (e.g. by crashing), we can receive a SIGPIPE due to the receiving process no longer existing. This becomes an EPIPE, which becomes an: OSError: [Errno

[issue10963] subprocess can raise OSError (EPIPE) when communicating with short-lived processes

2011-01-20 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: It could be argued that this is incorrect, as it masks under-reads of stdin by the subprocess. However I believe a sanely-written subprocess ought to indicate success/failure back with its return code. It seems quite orthogonal. The