[TIP] cleanUp for unittest

Douglas Philips dgou at mac.com
Fri Apr 3 18:19:47 PDT 2009

On or about 2009 Apr 3, at 6:27 PM, Robert Collins indited:
> I'd like to note that having it as a method gives the opportunity to  
> do
> different things in subclasses and that can be useful (and it also
> allows for better encapsulation etc.
> Anyhow, my main point: Unless someone says 'don't do it' I'll put a
> patch up for unittest in the patch tracker to add this.

Still no answer to the question: What is the purpose of tearDown once  
this is added?
When should I put code into tearDown (if at all) once this is available?


More information about the testing-in-python mailing list