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
Date 2009-04-04.16:10:31
SpamBayes Score 2.931883e-06
Marked as misclassified No
Message-id <1238861444.89.0.426269303954.issue5679@psf.upfronthosting.co.za>
In-reply-to
Content
Patch attached.

No docs, if it is agreed I can apply I'll write docs.

After a long discussion we arrived at some semblance of consensus on the
Testing In Python mailing list that this was a good thing (tm).

Only one -1 (thought that cleanUp should be a method) and Holger Krekel
was only +0 because he thinks changes in unittest should be conservative
(but he isn't actually using it).

Many others were +1 - Fred Drake, Titus Brown, Laura Creighton, Robert
Collins, Jonathan Lange, Kumar McMillan and others.

It provides a clean and simple pattern for the cleaning up of resources
- avoiding the need for nested try finallys and the manual tracking of
resources. It can also avoid the need for duplication of cleanup code.
History
Date User Action Args
2009-04-04 16:10:45michael.foordsetrecipients: + michael.foord, gregory.p.smith
2009-04-04 16:10:44michael.foordsetmessageid: <1238861444.89.0.426269303954.issue5679@psf.upfronthosting.co.za>
2009-04-04 16:10:43michael.foordlinkissue5679 messages
2009-04-04 16:10:35michael.foordcreate