[Python-Dev] py3k and not equal; re names (original) (raw)
Barry Warsaw barry at python.org
Thu Feb 9 13:39:06 CET 2006
- Previous message: [Python-Dev] py3k and not equal; re names
- Next message: [Python-Dev] py3k and not equal; re names
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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 python. I tried to find a rationale for the dropping--perhaps there is some other object that will be represented (like an empty set). I'm sure there must be some reason, but just want to put a vote in for keeping this variety.
I've long advocated for keeping <> as I find it much more visually
distinctive when reading code.
-Barry
- Previous message: [Python-Dev] py3k and not equal; re names
- Next message: [Python-Dev] py3k and not equal; re names
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]