Python Unicode handling wins again -- mostly
wxjmfauth at gmail.com
wxjmfauth at gmail.com
Wed Dec 4 08:52:34 EST 2013
Le mardi 3 décembre 2013 15:26:45 UTC+1, Ethan Furman a écrit :
> On 12/02/2013 12:38 PM, Ethan Furman wrote:
>
> > On 11/29/2013 04:44 PM, Steven D'Aprano wrote:
>
> >>
>
> >> Out of the nine tests, Python 3.3 passes six, with three tests being
>
> >> failures or dubious. If you believe that the native string type should
>
> >> operate on code-points, then you'll think that Python does the right
>
> >> thing.
>
> >
>
> > I think Python is doing it correctly. If I want to operate on "clusters" I'll normalize the string first.
>
>
>
> Hrmm, well, after being educated ;) I think I may have to reverse my position. Given that not every cluster can be
>
> normalized to a single code point perhaps Python is doing it the best possible way. On the other hand, we have a
>
> uni*code* type, not a uni*char* type. Maybe 3.5 can have that. ;)
>
>
------
Yon intuitively pointed a very important feature
of "unicode". However, it is not necessary, this is
exactly what unicode does (when used properly).
jmf
More information about the Python-list
mailing list