[Python-Dev] py3k and not equal; re names

2006-02-09 Thread Smith
I'm wondering if it's just foolish consistency (to quote a PEP 8) that is calling for the dropping of in preference of only !=. I've used the former since the beginning in everything from basic, fortran, claris works, excel, gnumeric, and python. I tried to find a rationale for the

Re: [Python-Dev] py3k and not equal; re names

2006-02-09 Thread Barry Warsaw
On Feb 9, 2006, at 3:41 AM, Smith wrote: I'm wondering if it's just foolish consistency (to quote a PEP 8) that is calling for the dropping of in preference of only !=. I've used the former since the beginning in everything from basic, fortran, claris works, excel, gnumeric, and

Re: [Python-Dev] py3k and not equal; re names

2006-02-09 Thread Thomas Wouters
On Thu, Feb 09, 2006 at 07:39:06AM -0500, Barry Warsaw wrote: I've long advocated for keeping as I find it much more visually distinctive when reading code. +1. And, two years ago, in his PyCon keynote, Guido forgot to say was going away, so I think Barry and I are completely in our rights

Re: [Python-Dev] py3k and not equal; re names

2006-02-09 Thread Barry Warsaw
On Thu, 2006-02-09 at 19:10 -0500, Jim Jewett wrote: Logically, = means the same as or = does not mean the same as or ; it might just mean that they aren't comparable. Whether that is a strong enough reason to remove it is another question. Visually, == looks very symmetrical and