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 ngie
Recipients gregory.p.smith, michael.foord, ngie, pitrou, rbcollins, vdupras
Date 2009-04-05.21:48:25
SpamBayes Score 0.0012451328
Marked as misclassified No
Message-id <1238968106.91.0.55233928845.issue5679@psf.upfronthosting.co.za>
In-reply-to
Content
I see the validity in the concern raised by Virgil:

I think this can be simplified from a user perspective by saying `I'm
electing to use cleanUp over tearDown'. The two systems are similar, but
also very different semantically as tearDown gets executed in the event
of test completion (regardless of whether or not it passed) whereas
cleanUp gets executed based on what occurs in setUp.

Or am I missing the boat here on what's trying to be accomplished?

We really shouldn't be mixing and matching both implementations because
that will confuse people...
History
Date User Action Args
2009-04-05 21:48:26ngiesetrecipients: + ngie, gregory.p.smith, pitrou, rbcollins, vdupras, michael.foord
2009-04-05 21:48:26ngiesetmessageid: <1238968106.91.0.55233928845.issue5679@psf.upfronthosting.co.za>
2009-04-05 21:48:25ngielinkissue5679 messages
2009-04-05 21:48:25ngiecreate