[Python-Dev] str object going in Py3K (original) (raw)
Fuzzyman fuzzyman at voidspace.org.uk
Tue Feb 14 10:29:37 CET 2006
- Previous message: [Python-Dev] PEP 332 revival in coordination with pep 349? [ Was:Re: release plan for 2.5 ?]
- Next message: [Python-Dev] str object going in Py3K
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Guido van Rossum wrote:
[snip..]
In py3k, when the str object is eliminated, then what do you have? Perhaps - bytes("\x80"), you get an error, encoding is required. There is no such thing as "default encoding" anymore, as there's no str object. - bytes("\x80", encoding="latin-1"), you get a bytestring with a single byte of value 0x80.
Yes to both again. Slightly related question. Sorry for the tangent.
In Python 3K, when the string data-type has gone, what will
open(filename).read() return ? Will the object returned have a
decode method, to coerce to a unicode string ?
Also, what datatype will u'some string'.encode('ascii') return ?
I assume that when the bytes datatype is implemented, we will be
able to do open(filename, 'wb').write(bytes(somedata)) ? Hmmm... I
probably ought to read the bytes PEP and the Py3k one...
Just curious...
All the best,
Michael Foord
-- --Guido van Rossum (home page: http://www.python.org/~guido/)
- Previous message: [Python-Dev] PEP 332 revival in coordination with pep 349? [ Was:Re: release plan for 2.5 ?]
- Next message: [Python-Dev] str object going in Py3K
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]