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 eric.araujo, neologix, pitrou, r.david.murray, telmich
Date 2012-03-19.19:10:06
SpamBayes Score 3.82834e-05
Marked as misclassified No
Message-id <1332184207.58.0.42136612234.issue14228@psf.upfronthosting.co.za>
In-reply-to
Content
If one could distinguish that python had ended because of a sigint from the error code, then it would be possible for the caller to throw away stderr in that case.  I agree with the OP that that having to deal with the traceback when you know what you want instead is a bit of a pain, but it may be better than an unclean shutdown.  (I don't know if it is, because I don't know the possible failure modes from an unclean shutdown of the Python startup code).
History
Date User Action Args
2012-03-19 19:10:07r.david.murraysetrecipients: + r.david.murray, pitrou, eric.araujo, neologix, telmich
2012-03-19 19:10:07r.david.murraysetmessageid: <1332184207.58.0.42136612234.issue14228@psf.upfronthosting.co.za>
2012-03-19 19:10:07r.david.murraylinkissue14228 messages
2012-03-19 19:10:06r.david.murraycreate