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 vdupras
Recipients gregory.p.smith, michael.foord, ngie, pitrou, rbcollins, vdupras
Date 2009-04-05.21:26:29
SpamBayes Score 8.0776624e-10
Marked as misclassified No
Message-id <>
So, we are talking about adding a feature that could cause problem whether 
cleanup is performed before tearDown or after tearDown. Don't we risk 
confusing developers who are not familiar with the cleanup order?

Do we really want to add this feature? The added functionality doesn't 
seem so attractive compared to the risk of confusion. We might as well 
continue to let the developers implement this feature in their own 
TestCase subclasses (for example, my own subclass already implement a 
TestCase.create_tmpdir(name) (which does cleanup, of course), which is 
easier to use than the rmtree example that was given as a use case). At 
least, when they do, they know about the cleanup order.
Date User Action Args
2009-04-05 21:26:31vduprassetrecipients: + vdupras, gregory.p.smith, pitrou, rbcollins, ngie, michael.foord
2009-04-05 21:26:31vduprassetmessageid: <>
2009-04-05 21:26:30vdupraslinkissue5679 messages
2009-04-05 21:26:30vduprascreate