Why prefer != over <> for Python 3.0?

[Torsten Bronger]

Re: Why prefer != over &lt;&gt; for Python 3.0?

Hallöchen!

Jorge Vargas writes:

On Tue, Apr 1, 2008 at 6:03 AM, Gabriel Genellina
<gagsl-py2@yahoo.com.a rwrote:
>

>[...]
>>
> I think it should be easy to add support for ≠≤≥ and even λ,
> only the tokenizer has to be changed.
>>

show me a keyboard that has those symbols and I'm all up for it.

For <= I have to press three buttons, for ≤ I have to press four
buttons. Not much of a difference. ;-)

However, I'm slightly disappointed with the UTF-8 support in some
mail clients involved in this thread, so Unicode surely has not
arrived yet.

Tschö,
Torsten.

--
Torsten Bronger, aquisgrana, europa vetus
Jabber ID: bronger@jabber. org
(See http://ime.webhop.org for further contact info.)

[Ben Finney]

Re: Why prefer != over &lt;&gt; for Python 3.0?

Torsten Bronger <bronger@physik .rwth-aachen.dewrites :

However, I'm slightly disappointed with the UTF-8 support in some
mail clients involved in this thread, so Unicode surely has not
arrived yet.

Want <URL:http://www.cafepress.c om/nucleartacos.26 721820>.

--
\ "bash awk grep perl sed, df du, du-du du-du, vi troff su fsck |
`\ rm * halt LART LART LART!" -- The Swedish BOFH, |
_o__) alt.sysadmin.re covery |
Ben Finney

[Gabriel Genellina]

Re: Why prefer != over &lt;&gt; for Python 3.0?

En Tue, 01 Apr 2008 04:15:57 -0300, Jorge Vargas <jorge.vargas@g mail.com>
escribió:

as for the original question, the point of going unicode is not to
make code unicode, but to make code's output unicode. thin of print
calls and templates and comments the world's complexity in languages.
sadly most english speaking people think unicode is irrelevant because
ASCII has everything, but their narrow world is what's wrong.

Python 3 is a good step in that direction. Strings are unicode,
identifiers are not restricted to ASCII, and the default source encoding
is not ASCII anymore (but I don't remember which one).
So this is now possible with 3.0:

>>año = 2008
>>print("halagü eño")

halagüeño

>>print("halagü eño".encode("la tin1"))

b'halag\xfce\xf 1o'

--
Gabriel Genellina

[Steve Holden]

Re: Why prefer != over &lt;&gt; for Python 3.0?

Torsten Bronger wrote:

Hallöchen!
>
Jorge Vargas writes:
>

>On Tue, Apr 1, 2008 at 6:03 AM, Gabriel Genellina
><gagsl-py2@yahoo.com.a rwrote:
>>

>>[...]
>>>
>> I think it should be easy to add support for ≠≤≥ and even λ,
>> only the tokenizer has to be changed.
>>>

>show me a keyboard that has those symbols and I'm all up for it.

>
For <= I have to press three buttons, for ≤ I have to press four
buttons. Not much of a difference. ;-)
>
However, I'm slightly disappointed with the UTF-8 support in some
mail clients involved in this thread, so Unicode surely has not
arrived yet.
>

I'd settle for a program listing utility that made the replacements.

regards
Steve
--
Steve Holden +1 571 484 6266 +1 800 494 3119
Holden Web LLC http://www.holdenweb.com/

[Steve Holden]

Re: Why prefer != over &lt;&gt; for Python 3.0?

Torsten Bronger wrote:

Hallöchen!
>
Jorge Vargas writes:
>

>On Tue, Apr 1, 2008 at 6:03 AM, Gabriel Genellina
><gagsl-py2@yahoo.com.a rwrote:
>>

>>[...]
>>>
>> I think it should be easy to add support for ≠≤≥ and even λ,
>> only the tokenizer has to be changed.
>>>

>show me a keyboard that has those symbols and I'm all up for it.

>
For <= I have to press three buttons, for ≤ I have to press four
buttons. Not much of a difference. ;-)
>
However, I'm slightly disappointed with the UTF-8 support in some
mail clients involved in this thread, so Unicode surely has not
arrived yet.
>

I'd settle for a program listing utility that made the replacements.

regards
Steve
--
Steve Holden +1 571 484 6266 +1 800 494 3119
Holden Web LLC http://www.holdenweb.com/

[John J. Lee]

Re: Why prefer != over &lt;&gt; for Python 3.0?

"Gabriel Genellina" <gagsl-py2@yahoo.com.a rwrites:
[...]

>There was a version of APL for the Sinclair QL which replaced the
>standard APL symbols with keywords.

>
Wow, APL on 8 bits?
Now there is (or perhaps there was) J, a reincarnation of APL by
Iverson himself that uses ASCII characters only.

The BBC Model B ran I-APL, too.

Sitting on my desk is a copy of "I-APL Instruction Manual for PC
Clones, RML Nimbus, BBC Master & B, and Archimedes", along with a few
other APL books and a pile of newsletters, waiting to be thrown away
:-( I got a copy because they were giving it away free to schools.
Poisoning young minds ;-)

How did programmers manage back then in 32k? Less software
development, more jigsaw puzzle.


John

[MRAB]

Re: Why prefer != over &lt;&gt; for Python 3.0?

On Mar 30, 7:59 pm, "Gabriel Genellina" <gagsl-...@yahoo.com.a r>
wrote:

En Sun, 30 Mar 2008 11:10:20 -0300, MRAB <goo...@mrabarn ett.plus.com>
escribió:
>
>
>

On Mar 30, 6:35 am, "Gabriel Genellina" <gagsl-...@yahoo.com.a r>
wrote:

En Sun, 30 Mar 2008 02:11:33 -0300, hdante <hda...@gmail.c omescribió:

>

BTW, my opinion is that it's already time that programmer editors
have input methods advanced enough for generating this:

>

if x ≠ 0:
∀y ∈ s:
if y ≥ 0: f1(y)
else: f2(y)

>

Fine if you have the right keyboard... Try to write APL with a standard
keyboard :)

>

There was a version of APL for the Sinclair QL which replaced the
standard APL symbols with keywords.

>
Wow, APL on 8 bits?
Now there is (or perhaps there was) J, a reincarnation of APL by Iverson
himself that uses ASCII characters only.
>

The Sinclair QL used the Motorola 68008, which was like the 68000 (a
32-bit processor) but with an 8-bit external data bus instead of a 16-
bit one; that made the system cheaper to build, but as the
instructions were multiples of 16 bits long every instruction required
at least 2 memory accesses, which made it slower. Nice clean processor
though, unlike the 8086... :-)