Differences of "!=" operator behavior in python3 and python2 [ bug? ]

[Chris Angelico]

On Tue, May 14, 2013 at 9:22 AM, Dave Angel <davea at davea.name> wrote:
> On 05/13/2013 06:53 PM, Mark Lawrence wrote:
>> I much prefer the alternative <> for != but some silly people insisted
>> that this be removed from Python3.  Just how stupid can you get?
>>
>
> So which special methods should the <> operator call?  By rights it ought to
> call both __gt__ and __lt__ and return True if either of them is True.

Why do you think that? After all, the != operator doesn't call
__factorial__ and __assignment__ and return True if either is True,
does it?

ChrisA

PS. :-)