Author r.david.murray
Recipients barry, ezio.melotti, michael.foord, r.david.murray, rbcollins, serhiy.storchaka, taleinat
Date 2015-06-13.14:57:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1434207436.02.0.942240060547.issue24412@psf.upfronthosting.co.za>
In-reply-to
Content
Not having addClassCleanup means that my setUpClass method will have four try/excepts in it, as will my tearDownClass (I have four fixtures I'm setting up for the tests).

So, no, it isn't strictly needed, but it is prettier :).  As Robert says, though, it makes for a nice symmetry in the API.  Basically, I like to see tearDown deprecated, as I find the setup/addcleanup pattern much easier to write and, more importantly, to read.
History
Date User Action Args
2015-06-13 14:57:16r.david.murraysetrecipients: + r.david.murray, barry, taleinat, rbcollins, ezio.melotti, michael.foord, serhiy.storchaka
2015-06-13 14:57:16r.david.murraysetmessageid: <1434207436.02.0.942240060547.issue24412@psf.upfronthosting.co.za>
2015-06-13 14:57:16r.david.murraylinkissue24412 messages
2015-06-13 14:57:15r.david.murraycreate