[issue9857] SkipTest in tearDown is reported an as an error

Michael Foord added the comment: Correction, the fix is combined with the fix for issue 10611. -- ___ Python tracker ___ ___ Python-bu

[issue9857] SkipTest in tearDown is reported an as an error

Michael Foord added the comment: Committed revision 87390. It is a stretch to see this as a bugfix rather than a new feature so probably *shouldn't* be backported to 2.7. On the other hand the fix is combined with the fix for issue 9857 which *is* a bugfix and *should* be backported to Python

[issue9857] SkipTest in tearDown is reported an as an error

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue9857] SkipTest in tearDown is reported an as an error

Mark Roddy added the comment: Attaching patch which does the same as the previous for the release27-maint branch. -- Added file: http://bugs.python.org/file19527/python27.skipteardown.patch ___ Python tracker

[issue9857] SkipTest in tearDown is reported an as an error

Mark Roddy added the comment: Attaching patch which adds support for registering a skip when raised from tearDown. Per Michael's point regarding failed tests, this is only handled if the test has been successful when SkipTest is raised from tearDown. -- keywords: +patch nosy: +MarkRo

[issue9857] SkipTest in tearDown is reported an as an error

Changes by Raghuram Devarakonda : -- nosy: +draghuram ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue9857] SkipTest in tearDown is reported an as an error

Michael Foord added the comment: Interesting use case. If the test has not yet failed this is fine. The problem is that if an exception has *already* been raised then it will already have been added to the result - so by then skipping is meaningless (or contradictory - the test can fail *and

[issue9857] SkipTest in tearDown is reported an as an error

New submission from Antoine Pitrou : Raising SkipTest when in a tearDown method is reported as an error, rather than a skipped test. Now doing this sounds like a weird use case, but it would be actually useful when you have a worker thread, and the tearDown method collects the exception raised