Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2000-May/004025.html below:

[Python-Dev] global encoding?!? (was: [Python-checkins] ... unicodeobject.c)

• Previous message: [Python-Dev] global encoding?!? (was: [Python-checkins] ... unicodeobject.c)
• Next message: [Python-Dev] global encoding?!? (was: [Python-checkins] ... unicodeobject.c)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Tue, 9 May 2000, Guido van Rossum wrote:
>...
> Watch your language.

Yes, Dad :-) Sorry...

> Marc did this at my request.  It is my intention that the encoding be
> hardcoded at compile time.  But while there's a discussion going about
> what the hardcoded encoding should *be*, it would seem handy to have a
> quick way to experiment.

Okee dokee... That was one of my questions: is this experimental or not?

It is still a bit frightening, though, if it might get left in there, for
the reasons I listed (to name a few) ... :-(

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/

• Previous message: [Python-Dev] global encoding?!? (was: [Python-checkins] ... unicodeobject.c)
• Next message: [Python-Dev] global encoding?!? (was: [Python-checkins] ... unicodeobject.c)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4