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 gregory.p.smith, michael.foord, pitrou, rbcollins
Date 2009-04-04.23:02:13
SpamBayes Score 2.8851244e-05
Marked as misclassified No
Message-id <1238886135.58.0.221288891971.issue5679@psf.upfronthosting.co.za>
In-reply-to
Content
Antoine, Robert suggests calling it after tearDown so that tearDown can
also perform actions that need clean up. Not a common use case but at
least a use case. What do you mean by: 

"so that test cases can also use it to initialize
additional resources and finalize them in a LIFO way wrt the main tearDown"

Can you give an example? You seem to imply that clean up be used to
initialize resources which seems very odd.
History
Date User Action Args
2009-04-04 23:02:15michael.foordsetrecipients: + michael.foord, gregory.p.smith, pitrou, rbcollins
2009-04-04 23:02:15michael.foordsetmessageid: <1238886135.58.0.221288891971.issue5679@psf.upfronthosting.co.za>
2009-04-04 23:02:14michael.foordlinkissue5679 messages
2009-04-04 23:02:13michael.foordcreate