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 rbcollins
Recipients ezio.melotti, michael.foord, pitrou, r.david.murray, rbcollins, serhiy.storchaka, terry.reedy, zach.ware
Date 2013-07-23.08:26:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1374567991.95.0.431598002992.issue18526@psf.upfronthosting.co.za>
In-reply-to
Content
I'll do a full review shortly, but at the conceptual level, I don't see any benefit in making a new SkipTest base class, other than instantly breaking other runners when an unknown exception is raised. SkipTest is part of the API. Making a new exception part of the API requires a strong reason - not just 'we want to show it differently' but 'we want the runner to behave differently.
History
Date User Action Args
2013-07-23 08:26:32rbcollinssetrecipients: + rbcollins, terry.reedy, pitrou, ezio.melotti, r.david.murray, michael.foord, zach.ware, serhiy.storchaka
2013-07-23 08:26:31rbcollinssetmessageid: <1374567991.95.0.431598002992.issue18526@psf.upfronthosting.co.za>
2013-07-23 08:26:31rbcollinslinkissue18526 messages
2013-07-23 08:26:31rbcollinscreate