Ethan Furman wrote:
On 06/30/2014 12:34 PM, Peter Otten wrote:
RainyDay wrote:
def __eq__(self, other):
return self._loc == getattr(other, _loc, None)
Note that None is not a good default when _loc is expected to be a tuple:
In this case None is not being returned, but
Hi, in python 3.4.1, I get this surpising behaviour:
l=Loc(0,0)
l2=Loc(1,1)
ll2
False
ll2
True
l=l2
Traceback (most recent call last):
File stdin, line 1, in module
TypeError: unorderable types: Loc() = Loc()
l==l2
False
ll2 or l==l2
True
Loc implements both __lt__ and __eq__, which
RainyDay wrote:
Hi, in python 3.4.1, I get this surpising behaviour:
l=Loc(0,0)
l2=Loc(1,1)
ll2
False
ll2
True
l=l2
Traceback (most recent call last):
File stdin, line 1, in module
TypeError: unorderable types: Loc() = Loc()
l==l2
False
ll2 or l==l2
True
Loc implements both
On Monday, June 30, 2014 3:34:25 PM UTC-4, Peter Otten wrote:
RainyDay wrote:
Hi, in python 3.4.1, I get this surpising behaviour:
l=Loc(0,0)
l2=Loc(1,1)
ll2
False
ll2
True
l=l2
Traceback (most recent call last):
File stdin, line 1, in module
On 06/30/2014 12:34 PM, Peter Otten wrote:
RainyDay wrote:
def __eq__(self, other):
return self._loc == getattr(other, _loc, None)
Note that None is not a good default when _loc is expected to be a tuple:
In this case None is not being returned, but will be comparid with
