Borrowing the documentation from the __contains__
documentation
print set.__contains__.__开发者_C百科doc__
x.__contains__(y) <==> y in x.
This seems to work fine for primitive objects such as int, basestring, etc. But for user-defined objects that define the __ne__
and __eq__
methods, I get unexpected behavior. Here is a sample code:
class CA(object):
def __init__(self,name):
self.name = name
def __eq__(self,other):
if self.name == other.name:
return True
return False
def __ne__(self,other):
return not self.__eq__(other)
obj1 = CA('hello')
obj2 = CA('hello')
theList = [obj1,]
theSet = set(theList)
# Test 1: list
print (obj2 in theList) # return True
# Test 2: set weird
print (obj2 in theSet) # return False unexpected
# Test 3: iterating over the set
found = False
for x in theSet:
if x == obj2:
found = True
print found # return True
# Test 4: Typcasting the set to a list
print (obj2 in list(theSet)) # return True
So is this a bug or a feature?
For set
s and dicts
, you need to define __hash__
. Any two objects that are equal should hash the same in order to get consistent / expected behavior in set
s and dicts
.
I would reccomend using a _key
method, and then just referencing that anywhere you need the part of the item to compare, just as you call __eq__
from __ne__
instead of reimplementing it:
class CA(object):
def __init__(self,name):
self.name = name
def _key(self):
return type(self), self.name
def __hash__(self):
return hash(self._key())
def __eq__(self,other):
if self._key() == other._key():
return True
return False
def __ne__(self,other):
return not self.__eq__(other)
This is because CA
doesn't implement __hash__
A sensible implementation would be:
def __hash__(self):
return hash(self.name)
A set
hashes it's elements to allow a fast lookup. You have to overwrite the __hash__
method so that a element can be found:
class CA(object):
def __hash__(self):
return hash(self.name)
Lists don't use hashing, but compare each element like your for
loop does.
精彩评论