X-Received: by 10.182.130.200 with SMTP id og8mr847320obb.18.1399529048378; Wed, 07 May 2014 23:04:08 -0700 (PDT)
X-Received: by 10.140.44.75 with SMTP id f69mr13292qga.11.1399529048352; Wed, 07 May 2014 23:04:08 -0700 (PDT)
Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!r10no1805632igi.0!news-out.google.com!dz10ni35687qab.1!nntp.google.com!ih12no1405676qab.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.python
Date: Wed, 7 May 2014 23:04:07 -0700 (PDT)
In-Reply-To: <mailman.9631.1398964881.18130.python-list@python.org>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=2a02:120b:2c6f:21f0:1c92:2b3:d9fc:9d75; posting-account=ung4FAoAAAC46zhHJ0Nsnuox7M5gDvs_
NNTP-Posting-Host: 2a02:120b:2c6f:21f0:1c92:2b3:d9fc:9d75
References: <0f253434-5e7d-4eea-88e1-7997fec2bd2d@googlegroups.com> <mailman.9452.1398232238.18130.python-list@python.org> <773afa7d-4b6d-4d67-8d40-ea90b335a1a2@googlegroups.com> <5357715c$0$11109$c3e8da3@news.astraweb.com> <aa55b40a-9032-401c-a24d-1b7518ebe1e1@googlegroups.com> <03bb12d8-93be-4ef6-94ae-4a02789aea2d@googlegroups.com> <ljfo63$5lq$1@ger.gmane.org> <mailman.9518.1398519519.18130.python-list@python.org> <bcd76ee0-4703-45ed-95c3-ad0cac35a889@googlegroups.com> <mailman.9631.1398964881.18130.python-list@python.org>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <90b5fb36-e99d-4dcb-8df0-77044ff53be9@googlegroups.com>
Subject: Re: Unicode in Python
From: wxjmfauth@gmail.com
Injection-Date: Thu, 08 May 2014 06:04:08 +0000
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Xref: csiph.com comp.lang.python:71078

Le jeudi 1 mai 2014 19:21:14 UTC+2, rand...@fastmail.us a =E9crit=A0:
> On Mon, Apr 28, 2014, at 4:57, wxjmfauth@gmail.com wrote:
>=20
> > Python 3:
>=20
> > - It missed the unicode shift.
>=20
> > - Covering the whole unicode range will not make
>=20
> > Python a unicode compliant product.
>=20
>=20
>=20
> Please cite exactly what portion of the unicode standard requires
>=20
> operations with all characters to be handled in the same amount of time
>=20
> and space, and forbids optimizations that make some characters handled
>=20
> faster or in less space than others.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

I missed you comment. Regression is only a side effect.

I can make Python failing (lead Python to failures) with
any piece of text or valid sequence of characters I wish [*].

I'm no more writing code (apps), only maintaining
my interactive interpreters.

[*] I do not count as failures, issues like cp65001,
only "basic" text/string manipulations.

jmf