To: python-list@python.org
From: Terry Reedy <tjreedy@udel.edu>
Subject: Re: Python discussed in Nature
Date: Fri, 13 Feb 2015 00:24:35 -0500
References: <54dc6870$0$12981$c3e8da3$5496439d@news.astraweb.com> <6322f4fa-c8af-4051-b6c6-ff953bd928ca@googlegroups.com> <mbi1id$4eb$1@speranza.aioe.org> <3bfcd265-fb89-431c-b9b6-94b24b2ef025@googlegroups.com> <31d8de6c-b368-4a46-a472-e77bb48bb2da@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
In-Reply-To: <31d8de6c-b368-4a46-a472-e77bb48bb2da@googlegroups.com>
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.18721.1423805089.18130.python-list@python.org>
Lines: 64
NNTP-Posting-Host: 2001:888:2000:d::a6
Path: csiph.com!usenet.pasdenom.info!bete-des-vosges.org!feed.ac-versailles.fr!nerim.net!novso.com!newsfeed.xs4all.nl!newsfeed4a.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Xref: csiph.com comp.lang.python:85629

On 2/12/2015 11:07 PM, Rustom Mody wrote:
> On Thursday, February 12, 2015 at 11:59:55 PM UTC+5:30, John Ladasky wr=
ote:
>> On Thursday, February 12, 2015 at 3:08:10 AM UTC-8, Fabien wrote:
>>
>>> ... what a coincidence then that a huge majority of scientists
>>> (including me) dont care AT ALL about unicode. But since scientists a=
re
>>> not paid to rewrite old code, the scientific world is still stuck to
>>> python 2.
>>
>> I'm a scientist.  I'm a happy Python 3 user who migrated from Python 2=
 about two years ago.
>>
>> And I use Unicode in my Python.  In implementing some mathematical mod=
els which have variables like delta, gamma, and theta, I decided that I d=
idn't like the line lengths I was getting with such variable names.  I'm =
using =CE=B4, =CE=B3, and =CE=B8 instead.  It works fine, at least on my =
Ubuntu Linux system (and what scientist doesn't use Linux?).  I also have=
 special mathematical symbols, superscripted numbers, etc. in my program =
comments.  It's easier to read 2x=C2=B3 + 3x=C2=B2 than 2*x**3 + 3*x**2.
>>
>> I am teaching someone Python who is having a few problems with Unicode=
 on his Windows 7 machine.  It would appear that Windows shipped with a l=
ess-than-complete Unicode font for its command shell.  But that's not Pyt=
hon's fault.
>
> Haskell is a bit ahead of python in this respect:
>
> Prelude> let (x=E2=82=81 , x=E2=82=82) =3D (1,2)
> Prelude> (x=E2=82=81 , x=E2=82=82)
> (1,2)
>
>>>> (x=E2=82=81 , x=E2=82=82) =3D (1,2)
>    File "<stdin>", line 1
>      (x=E2=82=81 , x=E2=82=82) =3D (1,2)
>        ^
> SyntaxError: invalid character in identifier
>
> But python is ahead in another (arguably more) important aspect:
> Haskell gets confused by ligatures in identifiers; python gets them rig=
ht
>
>>>> =EF=AC=82ag =3D 1
>>>> flag
> 1
>
> Prelude> let =EF=AC=82ag =3D 1
> Prelude> flag
>
> <interactive>:4:1: Not in scope: `flag'
>
> Hopefully python will widen its identifier-chars also

Python (supposedly) follows the Unicode definition based on character=20
classes, as documented.  If the Unicode definition in fact allows=20
subscripts, then Python should also.  If you want Python to broaden its=20
definition beyond unicode, you will have to advocate and persuade.  It=20
will not 'just happen'.

--=20
Terry Jan Reedy