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 | zanella |
|---|---|
| Recipients | jrosdahl, zanella |
| Date | 2008年05月19日.18:08:25 |
| SpamBayes Score | 0.2024153 |
| Marked as misclassified | No |
| Message-id | <1211220506.7.0.699251035327.issue2791@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I don't know a lot about the matter at hand, that's why I'm not gonna append a patch. On "_communicate()" after a pipe is read it's closed, doing the same on "communicate()" seems to solve the issue of the extra pipe: """ if [self.stdin, self.stdout, self.stderr].count(None) >= 2: stdout = None stderr = None if self.stdin: if input: self.stdin.write(input) self.stdin.close() elif self.stdout: stdout = self.stdout.read() + self.stdout.close() elif self.stderr: stderr = self.stderr.read() + self.stderr.close() self.wait() return (stdout, stderr) """ Tested on "Python 2.6a2+ (trunk:62767M, May 19 2008, 13:11:07)". |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年05月19日 18:08:27 | zanella | set | spambayes_score: 0.202415 -> 0.2024153 recipients: + zanella, jrosdahl |
| 2008年05月19日 18:08:26 | zanella | set | spambayes_score: 0.202415 -> 0.202415 messageid: <1211220506.7.0.699251035327.issue2791@psf.upfronthosting.co.za> |
| 2008年05月19日 18:08:25 | zanella | link | issue2791 messages |
| 2008年05月19日 18:08:25 | zanella | create | |