[TIP] always call teardownX even if setupX fails?

Robert Collins robertc at robertcollins.net
Sat Jan 23 02:51:59 PST 2010

On Sat, 2010-01-23 at 00:43 +0100, holger krekel wrote:
> Doesn't look like a blocker to me at the moment.  What do you think? 
> Any objections or recommendations?  Do you regard consistency a
> blocker? 

Trial and testtools run tearDown unconditionally even though its
inconsistent with unittest. I'm a big fan of doing that, and encourage
you to do it in py.test.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://lists.idyll.org/pipermail/testing-in-python/attachments/20100123/e88ccc90/attachment.pgp>

More information about the testing-in-python mailing list