On 5 December 2015 at 20:30, Noufal Ibrahim KV wrote:
> On Sat, Dec 05 2015, Gora Mohanty wrote:
>
>
> [...]
>
>> Maybe because that was the historical way that C did it? I agree that
>> the Python 3 exception makes more sense.
>
> [...]
>
> We can only guess but you'll have to explicitly code thi
On Sat, Dec 05 2015, Gora Mohanty wrote:
[...]
> Maybe because that was the historical way that C did it? I agree that
> the Python 3 exception makes more sense.
[...]
We can only guess but you'll have to explicitly code this in and I can't
think of any situation where it would make sense.
-
On 5 December 2015 at 12:56, Noufal Ibrahim KV wrote:
>
>
> So I came across this today..
>
> >>> class Number(object):
> ...def __init__(self, n):
> ... self.n = n
> ...
> >>> m = Number(10)
> >>> n = Number(5)
> >>>
> >>> m < n
> True
>
> This is documented like so
>
> > If no __cmp__(
On Sat, Dec 05 2015, Anand Chitipothu wrote:
[...]
> Thats why you should use Python 3. Here is what you get with Python 3.
[...]
Yet another reason to move. I'm still curious why they did it the other
way in 2.x though.
--
Cordially,
Noufal
http://nibrahim.net.in
__
On Sat, Dec 5, 2015 at 12:56 PM, Noufal Ibrahim KV
wrote:
>
> So I came across this today..
>
> >>> class Number(object):
> ...def __init__(self, n):
> ... self.n = n
> ...
> >>> m = Number(10)
> >>> n = Number(5)
> >>>
> >>> m < n
> True
>
> This is documented like so
>
> > If no __cmp
So I came across this today..
>>> class Number(object):
...def __init__(self, n):
... self.n = n
...
>>> m = Number(10)
>>> n = Number(5)
>>>
>>> m < n
True
This is documented like so
> If no __cmp__(), __eq__() or __ne__() operation is defined, class
> instances are compared by obj