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 r.david.murray
Recipients Cal.Leeming, gregory.p.smith, neologix, r.david.murray
Date 2011-06-01.17:19:37
SpamBayes Score 0.0001043911
Marked as misclassified No
Message-id <1306948778.22.0.663004787239.issue12235@psf.upfronthosting.co.za>
In-reply-to
Content
Subprocess is throwing the correct exception, what it isn't doing is preserving stderr.  The stderr output in question is not coming from the *subprocess* (the process hasn't been created yet).  It would be nice if that stderr output could be added to the exception message, but that is not normally the way os errors are handled in python.
History
Date User Action Args
2011-06-01 17:19:38r.david.murraysetrecipients: + r.david.murray, gregory.p.smith, neologix, Cal.Leeming
2011-06-01 17:19:38r.david.murraysetmessageid: <1306948778.22.0.663004787239.issue12235@psf.upfronthosting.co.za>
2011-06-01 17:19:37r.david.murraylinkissue12235 messages
2011-06-01 17:19:37r.david.murraycreate