Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #45271
| Date | 2013-05-14 09:30 +1000 |
|---|---|
| From | Cameron Simpson <cs@zip.com.au> |
| Subject | Re: Differences of "!=" operator behavior in python3 and python2 [ bug? ] |
| References | <519175B0.90603@davea.name> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.1649.1368487859.3114.python-list@python.org> (permalink) |
On 13May2013 19:22, Dave Angel <davea@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@zip.com.au>
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Differences of "!=" operator behavior in python3 and python2 [ bug? ] Cameron Simpson <cs@zip.com.au> - 2013-05-14 09:30 +1000
csiph-web