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 flub
Recipients amaury.forgeotdarc, eric.araujo, flub, tarek
Date 2010-09-21.21:58:57
SpamBayes Score 3.8034221e-07
Marked as misclassified No
Message-id <1285106339.72.0.0616302848479.issue9912@psf.upfronthosting.co.za>
In-reply-to
Content
I'm aware of that but my limited testing showed that in this case that doesn't happen.

However if this is considered too brittle to just plain fail as soon as there's stderr, how about using distutils' log facility to log the stderr at a reasonable level (warning?)?  That way at least you'll be able to see something useful when you get a failure at a strange looking and far less meaningful traceback a few lines lower.
History
Date User Action Args
2010-09-21 21:58:59flubsetrecipients: + flub, amaury.forgeotdarc, tarek, eric.araujo
2010-09-21 21:58:59flubsetmessageid: <1285106339.72.0.0616302848479.issue9912@psf.upfronthosting.co.za>
2010-09-21 21:58:58flublinkissue9912 messages
2010-09-21 21:58:58flubcreate