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 pitrou
Recipients gregory.p.smith, michael.foord, ngie, pitrou, rbcollins, vdupras
Date 2009-04-05.21:31:38
SpamBayes Score 3.7054885e-08
Marked as misclassified No
Message-id <1238967185.6499.19.camel@fsol>
In-reply-to <>
> 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?

Well, we could do both. Call cleanups before tearDown (all the while
popping them), call tearDown, and call the new cleanups.

If the cleanup machinery is written carefully enough, you may even be
able to add another cleanup during a cleanup :-)
Date User Action Args
2009-04-05 21:31:39pitrousetrecipients: + pitrou, gregory.p.smith, rbcollins, vdupras, ngie, michael.foord
2009-04-05 21:31:38pitroulinkissue5679 messages
2009-04-05 21:31:38pitroucreate