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

[Cameron Simpson]

On 13May2013 19:22, 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.

Surely it should require both of them to be true...

Personally I'm for != given we have ==. Aside from notational
consistency it makes conceptual sense for unordered types, which
<> does not really.

Cheers,
-- 
Cameron Simpson <cs at zip.com.au>