On 8/24/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> Should I attempt to reproduce this bug in 2.5 and fix it?
Couldn't help myself. The fix is python.org/sf/1546288 . I set the
priority to 8 which means Neal and Anthony will look at it. It's
probably okay to reduce the priority to 7 and fix
On 8/24/06, Tim Peters <[EMAIL PROTECTED]> wrote:
> [Guido]
> > There's a unit test "test_mutants" which I don't understand. If anyone
> > remembers what it's doing, please contact me -- after ripping out
> > dictionary ordering in Py3k,
>
> Is any form of dictionary comparison still supported, and
On 8/24/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> I made that change, and changed class Horrid to define __eq__ instead
> of __cmp__. Since dict_equal() only invokes PyObject_RichCompareBool()
> with op==Py_EQ that should be all that's needed.
>
> Now when I run it, it spits out an apaprent
[Guido]
> There's a unit test "test_mutants" which I don't understand. If anyone
> remembers what it's doing, please contact me -- after ripping out
> dictionary ordering in Py3k,
Is any form of dictionary comparison still supported, and, if so, what
does "dict1 cmp_op dict2" mean now?
> it stops
There's a unit test "test_mutants" which I don't understand. If anyone
remembers what it's doing, please contact me -- after ripping out
dictionary ordering in Py3k, it stops working. In particular, the code
in test_one() requires changes, but I don't know how... Please help!
--
--Guido van Rossu
