Take the following example:
>>> class C(object):
... def __init__(self, p):
... self.p = p
... def __eq__(self, o):
... return True
...
>>>开发者_StackOverflow中文版 C(1) is C(2)
False
>>> C(1) == C(2)
True
>>> C(1) != C(2)
True # <- Why?!?
So now the two objects are equal and not-equal at the same time. I though the two operations are opposing?!
Python’s “Data model” explains it all:
There are no implied relationships among the comparison operators. The truth of
x==y
does not imply thatx!=y
is false. Accordingly, when defining__eq__()
, one should also define__ne__()
so that the operators will behave as expected.
In C(1) != C(2)
, it’s using the default implementation, where objects are equal only to themselves and unequal to everything else.
Defining __cmp__
can be simpler, as it is used as a fallback for all comparison operations, not just some of them:
... def __cmp__(self, o):
... return 0
>>> C(1) != C(2)
False
There is a separate function for !=
which is __ne__
which is implicitly defined to compare the instance members.
What you want to do is:
def __ne__(self, other):
return not self.__eq__(other)
or some variant of this.
You have to define both __ne__
and __eq__
. And you probably ought to consider implementing __cmp__
too!
精彩评论