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 r.david.murray
Recipients barry, ezio.melotti, michael.foord, r.david.murray, rbcollins, serhiy.storchaka, taleinat
Date 2015-06-19.22:51:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
That would not make it simpler.  In fact it would make the test code more complex.  I'd still need the safeSetUpClass dodge (or repeat the try/except/log in every setUpClass method), and I'd have to have a wrapper function that I passed each cleanup to as an argument to wrap it in a try/except/log, since close would just propagate the exceptions.  

I think implementing this parallel to addCleanUp is much cleaner, even if the feature isn't (yet :) in the stdlib.
Date User Action Args
2015-06-19 22:51:12r.david.murraysetrecipients: + r.david.murray, barry, taleinat, rbcollins, ezio.melotti, michael.foord, serhiy.storchaka
2015-06-19 22:51:12r.david.murraysetmessageid: <>
2015-06-19 22:51:12r.david.murraylinkissue24412 messages
2015-06-19 22:51:12r.david.murraycreate