[issue1615376] subprocess doesn\'t handle SIGPIPE

2011-02-05 Thread Gregory P. Smith
Gregory P. Smith added the comment: The need to call p1.stdout.close() has now been documented as part of issue7678. Python 3.2's subprocess also has restore_signals=True as its default behavior so SIGPIPE is restored by default. I do not think it is appropriate to to add the synchronization

[issue1615376] subprocess doesn\'t handle SIGPIPE

2011-01-03 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- assignee: astrand -> nosy: +gregory.p.smith ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue1615376] subprocess doesn\'t handle SIGPIPE

2010-09-27 Thread Barry A. Warsaw
Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue1615376] subprocess doesn\'t handle SIGPIPE

2010-08-08 Thread Terry J. Reedy
Changes by Terry J. Reedy : -- versions: +Python 3.2 -Python 2.7, Python 3.1 ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue1615376] subprocess doesn\'t handle SIGPIPE

2009-03-30 Thread Daniel Diniz
Daniel Diniz added the comment: Confirmed on trunk and py3k. -- nosy: +ajaksu2 stage: -> test needed versions: +Python 2.7, Python 3.1 ___ Python tracker ___