[crossposting to python-3000]
Martin v. Löwis schrieb:
[removing string->string codecs]
>>> You're not losing functionality -- these conversions will remain
>>> available by importing the appropriate module. You're losing a very
>>> minor amount of convenience.
>>
>> Of the mentioned encodings
On 5/11/06, Boris Borcic <[EMAIL PROTECTED]> wrote:
> I am late on this subthread, but FWIW and FYI with Python 2.4.2 and Idle 1.1.2
> on WinXP I can use non-ascii identifiers transparently both in modules and at
> the prompt, for instance
>
> >>> grüzi = râle = niño = ça = True
> >>> grüzi
> Tru
Thomas Heller <[EMAIL PROTECTED]> writes:
>> >>> grüzi = râle = niño = ça = True
>> >>> grüzi
>> True
>>
>> I thought it was a provided feature, but scanning the subthread gave the
>> contrary impression. Should we expect disappearance of the property ?
>
> This looks like an IDLE bug to me.
Boris Borcic wrote:
> Martin v. Löwis wrote:
> > Guido van Rossum wrote:
> >> I want good Unicode support for string literals and comments.
> >> Everything else in the language ought to be ASCII.
> >
> > Does that include restricting identifiers to ASCII as well?
>
> I am late on this subthre
Martin v. Löwis wrote:
> Guido van Rossum wrote:
>> I want good Unicode support for string literals and comments.
>> Everything else in the language ought to be ASCII.
>
> Does that include restricting identifiers to ASCII as well?
I am late on this subthread, but FWIW and FYI with Python 2.4
Martin v. Löwis wrote:
> It depends on the language you use to communicate. In English,
> it is certainly cumbersome to talk about Chinese identifiers.
> OTOH, I believe it is cumbersome to communicate about English
> identifiers in Chinese, either, because the speakers might
> not even know what
On 4/30/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Ok. I was only worried about your change in PEP 3099:
> "Python won't use Unicode characters for anything except string literals
> or comments."
> If that is only meant to say "this won't be introduced in Python 3",
> I'm fine with it.
Rig
Guido van Rossum wrote:
> But a file with "löwis=1" in it causes a syntax error (even if an
> encoding is specified).
That's because it gets converted to UTF-8 first, and then the UTF-8
bytes don't count as Latin-1 letters.
> I believe this is a quirk of interactive mode only. Certainly the
> lan
On 4/29/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Python 2.3.5 (#2, Mar 6 2006, 10:12:24)
> [GCC 4.0.3 20060304 (prerelease) (Debian 4.0.2-10)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> py> import locale
> py> locale.setlocale(locale.LC_ALL, "")
On 4/29/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On 4/28/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > Guido van Rossum wrote:
> > >> I was hoping to propose a PEP on non-ASCII identifiers some
> > >> day; that would (of course) include a requirement that the
> > >> standard library
Georg Brandl wrote:
> They'll still have to type, pronounce and talk about English keywords, English
> operators and English standard library and 3rd-party module, class and method
> names, which makes a big percentage of code still Latin.
They don't have to understand the English meaning of the k
Guido van Rossum wrote:
>> > But Unicode has many alternative sets digits for which "isdigit" is
>> true.
>>
>> You mean, the Python isdigit() method? Sure, but the tokenizer uses
>> the C isdigit function, which gives true only for [0-9].
>
> Isn't that because it's only defined on 8-bit characte
On 4/28/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Guido van Rossum wrote:
> >> The distinction of letters and digits is also straight-forward:
> >> a digit is ASCII [0-9]; it's a separate lexical class only
> >> because it plays a special role in (number) literals. More
> >> generally, the
Martin v. Löwis wrote:
> Guido van Rossum wrote:
>>> I was hoping to propose a PEP on non-ASCII identifiers some
>>> day; that would (of course) include a requirement that the
>>> standard library would always be restricted to ASCII-only
>>> identifiers as a style-guide.
>>
>> IMO communication ab
Guido van Rossum wrote:
>> The distinction of letters and digits is also straight-forward:
>> a digit is ASCII [0-9]; it's a separate lexical class only
>> because it plays a special role in (number) literals. More
>> generally, there is the distinction of starter and non-starter
>> characters.
>
On 4/28/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Guido van Rossum wrote:
> >> I was hoping to propose a PEP on non-ASCII identifiers some
> >> day; that would (of course) include a requirement that the
> >> standard library would always be restricted to ASCII-only
> >> identifiers as a st
Guido van Rossum wrote:
>> I was hoping to propose a PEP on non-ASCII identifiers some
>> day; that would (of course) include a requirement that the
>> standard library would always be restricted to ASCII-only
>> identifiers as a style-guide.
>
> IMO communication about code becomes much more cumb
On 4/28/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Guido van Rossum wrote:
> > I want good Unicode support for string literals and comments.
> > Everything else in the language ought to be ASCII.
>
> Does that include restricting identifiers to ASCII as well?
Yes, that's my intent.
> I wa
Guido van Rossum wrote:
> I want good Unicode support for string literals and comments.
> Everything else in the language ought to be ASCII.
Does that include restricting identifiers to ASCII as well?
I was hoping to propose a PEP on non-ASCII identifiers some
day; that would (of course) include
19 matches
Mail list logo
