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 sbt
Recipients Daniel.Blanchard, amaury.forgeotdarc, jnoller, nikratio, sbt, ysj.ray
Date 2012-05-01.11:57:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1335873466.9.0.181110538985.issue9400@psf.upfronthosting.co.za>
In-reply-to
Content
There are plenty of other "bad" exception classes apart from CalledProcessError, including TimeoutExpired in the same file.  In fact I suspect this is true of the majority of the exception classes in the stdlib which override __init__.  So I am not sure how much good it would do to fix just one example.

Python 3.x's Pool wraps bad exception instances in a MaybeEncodingError class which at least lets you see a stringification of the original exception.  I am not sure whether you would want to see a backport of this.  Even though 2.7 is in bug fix mode, I think a backport would still be appropriate since it stops a pickling error from killing a worker process, causing a hang.
History
Date User Action Args
2012-05-01 11:57:46sbtsetrecipients: + sbt, amaury.forgeotdarc, jnoller, nikratio, ysj.ray, Daniel.Blanchard
2012-05-01 11:57:46sbtsetmessageid: <1335873466.9.0.181110538985.issue9400@psf.upfronthosting.co.za>
2012-05-01 11:57:46sbtlinkissue9400 messages
2012-05-01 11:57:46sbtcreate