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 brett.cannon
Recipients brett.cannon, gfxmonk
Date 2009-03-22.03:30:17
SpamBayes Score 0.00013920914
Marked as misclassified No
Message-id <1237692619.94.0.774842210183.issue5531@psf.upfronthosting.co.za>
In-reply-to
Content
So I disagree with this idea. The point of a tearDown method is simply
to clean up, not to test for a failure. If the test failed because it
didn't complete a test and clean up after itself then the test should
fail explicitly, not have the tearDown do it for the test.
History
Date User Action Args
2009-03-22 03:30:20brett.cannonsetrecipients: + brett.cannon, gfxmonk
2009-03-22 03:30:19brett.cannonsetmessageid: <1237692619.94.0.774842210183.issue5531@psf.upfronthosting.co.za>
2009-03-22 03:30:17brett.cannonlinkissue5531 messages
2009-03-22 03:30:17brett.cannoncreate