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 michael.foord
Recipients eric.araujo, michael.foord, rbcollins, ysj.ray
Date 2014-11-07.11:15:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1415358915.23.0.792839773399.issue10611@psf.upfronthosting.co.za>
In-reply-to
Content
Allowing sys.exit() to end the test run was particularly a problem for testing command line tools, where improper patching / unexpected code paths would trigger a sys.exit.

If a test framework author wants a way to end the test run I'm happy to provide that (a custom exception to raise or a flag to turn off sys.exit handling), but I don't think having sys.exit kill test runs is best for test authors.
History
Date User Action Args
2014-11-07 11:15:15michael.foordsetrecipients: + michael.foord, rbcollins, eric.araujo, ysj.ray
2014-11-07 11:15:15michael.foordsetmessageid: <1415358915.23.0.792839773399.issue10611@psf.upfronthosting.co.za>
2014-11-07 11:15:15michael.foordlinkissue10611 messages
2014-11-07 11:15:14michael.foordcreate