inequality unexpected behavior with color objects

[skorokithakis]

In [1]: second_col.web
Out[1]: 'white'

In [2]: second_col == Color("white")
Out[2]: True

In [3]: second_col != Color("white")
Out[3]: True

[tommilligan]

Nice find! Good case for learning about custom comparisons for classes. Root cause was that the Color class has a custom __eq__ method, but no custom __ne__ method.

[skorokithakis]

Ah, right. You might want to define __ne__ as !__eq__, to make those complementary.

[skorokithakis]

(I.e. define one in terms of the other, that way there's no way to get something that's both equal and unequal to itself, no matter what the equality code does)

[tommilligan]

Yep - writing up a pull request now

[tommilligan]

When writing this I dindn't define __ne__ as !__eq__, as this may lead to evaluation of !NotImplemented (which gives False, rather than also NotImplemented).

Just checking now, and StackOverflow appears to agree they should not be nested - shame as it would be much simpler!

[skorokithakis]

I don't have time right now to read the post thoroughly, but it seems to indicate that if __ne__ raises NotImplementedError, Python will use the opposite of ==, no?

[tommilligan]

That wasn't the initial impression I got - but will go back and have another look. I think the way I've implemented it here at least works and fits in with the style of the module, but I will see if there are more pythonic idioms out there.

[vaab]

Please note that this does not happen on python 3. IMHO a fix (as proposed in #29) is to implement the missing behavior of python 2 exactly as it is done in python 3.
What do you think of this ?