➜

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 Doug Coleman
Recipients Daniel.Blanchard, Doug Coleman, amaury.forgeotdarc, bronger, davin, jnoller, mdengler, nikratio, python-dev, sbt, ysj.ray
Date 2016-09-01.23:30:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1472772619.92.0.727798275372.issue9400@psf.upfronthosting.co.za>
In-reply-to
Content 
Six years later and I'm still running into this exact bug with ``subprocess.CalledProcessError`` on python 2.7.12 when doing a ``multiprocessing.Pool.map`` and trying to catch errors from ``subprocess.check_output``. 

What's the reason it was never fixed and backported?
History
Date User Action Args
2016-09-01 23:30:20Doug Colemansetrecipients: + Doug Coleman, amaury.forgeotdarc, bronger, jnoller, nikratio, ysj.ray, python-dev, sbt, Daniel.Blanchard, mdengler, davin
2016-09-01 23:30:19Doug Colemansetmessageid: <1472772619.92.0.727798275372.issue9400@psf.upfronthosting.co.za>
2016-09-01 23:30:19Doug Colemanlinkissue9400 messages
2016-09-01 23:30:19Doug Colemancreate