[TIP] cleanUp for unittest

Olemis Lang olemis at gmail.com
Tue Apr 7 10:24:05 PDT 2009


On Tue, Apr 7, 2009 at 12:20 PM, Scott David Daniels
<Scott.Daniels at acm.org> wrote:
> Fred Drake wrote:
>>
>> On Tue, Apr 7, 2009 at 11:58 AM, Olemis Lang <olemis at gmail.com> wrote:
>>
>>>>
>>>> This relies on Python's garbage collector implementation details (i.e.
>>>> refcounting),
>>>>
>>>
>>> That's th idea ;)
>>>
>>
>> This seems to make it very easy to create fragile fixtures
>> unintentionally, since not all Python implementations share the same
>> garbage collection semantics.
>
> It is also conceivable that, in the event of a test failure, a reference is
> held longer
> into the test by virtue of the traceback itself being a reference for a
> while.  I'd
> not put it past some elaborate error reporting schemes to hold onto such
> things.

Oh yes, this seems to be a *BIG* reason against «GC tearDown».

-- 
Regards,

Olemis.

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article:
Se retira el BDFL ... ¿El fin de Python 3k?



More information about the testing-in-python mailing list