[Python-3000] Support for PEP 3131
Jim Jewett
jimjjewett at gmail.com
Mon Jun 11 23:59:12 CEST 2007
On 6/11/07, "Martin v. Löwis" <martin at v.loewis.de> wrote:
> Ka-Ping Yee schrieb:
> > Steve Howell wrote:
> >> I think this whole debate could be put to rest by
> >> agreeing to err on the side of ascii in 3.0 beta, and
> >> if in real world experience, that turns out to be the
> >> wrong decision, simply fix it in 3.0 production, 3.1,
> >> or 3.2.
> > On Sun, 10 Jun 2007, [ISO-8859-1] "Martin v. L�wis" wrote:
> >> Likewise, this whole debate could also be put to rest
> >> by agreeing to err on the side of unrestricted support
> >> for the PEP, and if that turns out to be the wrong
> >> decision, simply fix any problems discovered in 3.0
> >> production, 3.1, or 3.2.
> > Your attempted parallel does not match: it breaks code,
> > whereas Steve's does not.
> PEP 3131 does not break any code.
Going with the widest possible set of source characters (as PEP 3131
does) and restricting them later (in 3.1) would break code.
Going with a smaller set of possible source characters and expanding
them later would not break code.
Going with ASCII by default plus locally approved charset-extensions
would not break code unless the new restrictions overrode local
decisions.
-jJ
More information about the Python-3000
mailing list