[Python-Dev] PEP 332 revival in coordination with pep 349? [ Was:Re: release plan for 2.5 ?] (original) (raw)
Greg Ewing greg.ewing at canterbury.ac.nz
Wed Feb 15 02:59:24 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] PEP 332 revival in coordination with pep 349? [ Was:Re: release plan for 2.5 ?]
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Guido van Rossum wrote:
On 2/13/06, Phillip J. Eby <pje at telecommunity.com> wrote:
At 04:29 PM 2/13/2006 -0800, Guido van Rossum wrote:
On 2/13/06, Phillip J. Eby <pje at telecommunity.com> wrote:
What would bytes("abc\xf0", "latin-1") mean? I'm saying that XXX would be the same encoding as you specified. i.e., including an encoding means you are encoding the meaning of the string.
No, this is wrong. As I understand it, the encoding argument to bytes() is meant to specify how to encode characters into the bytes object. If you want to be able to specify how to decode a str argument as well, you'd need a third argument.
-- Greg Ewing, Computer Science Dept, +--------------------------------------+ University of Canterbury, | Carpe post meridiam! | Christchurch, New Zealand | (I'm not a morning person.) | greg.ewing at canterbury.ac.nz +--------------------------------------+
- Previous message: [Python-Dev] PEP 332 revival in coordination with pep 349? [ Was:Re: release plan for 2.5 ?]
- Next message: [Python-Dev] PEP 332 revival in coordination with pep 349? [ Was:Re: release plan for 2.5 ?]
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]