List Info

Thread: Re: incompatible unittest changes




Re: incompatible unittest changes
country flaguser name
United States
2007-10-19 18:01:14
On Fri, 19 Oct 2007 15:51:51 -0700, Collin Winter
<collinwgmail.com> wrote:
>On 10/19/07, Jean-Paul Calderone <exarkundivmod.com> wrote:
>> In trunk after 2.5, equality and hashing for
TestCase were added, changing the behavior so that two
instances of TestCase for the same test method hash the same
and compare equal.  This means two instances of TestCase for
the same test method cannot be added to a single set.
>>
>> Here's the change:
>>
>> http://svn.python.org
/view/python/trunk/Lib/unittest.py?rev=54199&r1=42115&am
p;r2=54199
>>
>> The implementations aren't even very good, since
they prevent another type from deciding that it wants to
customize comparison against TestCase (or TestSuite,
>> or FunctionTestCase) instances.
>
>The implementations have been changed in a more recent
revision.

Not in http://svn.python.org/projects/python/trunk/Lib/unitt
est.py58552

>
>> Is there a real use case for this functionality? 
If not, I'd like it to be
>> removed to restore the old behavior.
>
>The use-case was problems I encountered when writing the
test suite
>for unittest. If you can find a way to implement the
functionality you
>want *and* keep the test suite reasonably
straightforward, I'll be
>happy to review your patch.

The test suite can implement the comparison which is
currently on the
unittest classes and invoke that functionality instead of
using == and
!=.

Jean-Paul
_______________________________________________
Python-Dev mailing list
Python-Devpython.org
ht
tp://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/p
ython-dev/nessto%40sharedlog.com

[1]

about | contact  Other archives ( Real Estate discussion Medical topics )