Message 260403 - Python tracker

➜

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	akira
Recipients	akira, martin.panter, neologix, serhiy.storchaka, vstinner
Date	2016-02-17.17:07:49
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1455728870.07.0.0684992618726.issue23570@psf.upfronthosting.co.za>
In-reply-to

Content
Should this issue be reopened in light of http://bugs.python.org/issue26372 (Popen.communicate not ignoring BrokenPipeError)? If .close() shouldn't raise BrokenPipeError in .communicate() (and it shouldn't) then it seems logical that .close() shouldn't raise BrokenPipeError in .__exit__() too (and in other subprocess.Popen methods that do not return until the child process is dead such as subprocess.run())

Should this issue be reopened in light of
http://bugs.python.org/issue26372 (Popen.communicate not ignoring
BrokenPipeError)?

If .close() shouldn't raise BrokenPipeError in .communicate() (and it
shouldn't) then it seems logical that .close() shouldn't raise
BrokenPipeError in .__exit__() too (and in other subprocess.Popen
methods that do not return until the child process is dead such as
subprocess.run())

History
Date	User	Action	Args
2016-02-17 17:07:50	akira	set	recipients: + akira, vstinner, neologix, martin.panter, serhiy.storchaka
2016-02-17 17:07:50	akira	set	messageid: <1455728870.07.0.0684992618726.issue23570@psf.upfronthosting.co.za>
2016-02-17 17:07:50	akira	link	issue23570 messages
2016-02-17 17:07:49	akira	create