A RetroSearch Logo

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

Search Query:

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

[Python-Dev] Re: [Python-checkins] CVS: python/dist/src/Objects unicodeobject.c,2.21,2.22

[Python-Dev] Re: [Python-checkins] CVS: python/dist/src/Objects unicodeobject.c,2.21,2.22Greg Stein gstein@lyra.org
Wed, 7 Jun 2000 19:35:37 -0700
On Wed, Jun 07, 2000 at 02:13:24AM -0700, Marc-Andre Lemburg wrote:
> Update of /cvsroot/python/python/dist/src/Objects
> In directory slayer.i.sourceforge.net:/tmp/cvs-serv17917/Objects
> 
> Modified Files:
> 	unicodeobject.c 
> Log Message:
> Marc-Andre Lemburg <mal@lemburg.com>:
> Change the default encoding to 'ascii' (it was previously
> defined as UTF-8).
> 
> Note: The implementation still uses UTF-8 to implement
> the buffer protocol, so C APIs will still see UTF-8. This
> is on purpose: rather than fixing the Unicode implementation,
> the C APIs should be made Unicode aware.

I'm a little confused on where this gets applied. Is this when somebody says
"str(unicode_ob)", they get back ASCII rather than UTF-8? Or is this when
somebody says "unicode(str)" and we expect <str> to be ASCII?

Cheers,
-g

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



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