[Python-Dev] PEP 332 revival in coordination with pep 349? [ Was:Re: release plan for 2.5 ?]
Adam Olsen
rhamph at gmail.com
Wed Feb 15 06:02:32 CET 2006
More information about the Python-Dev mailing list
Wed Feb 15 06:02:32 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 ]
On 2/14/06, Guido van Rossum <guido at python.org> wrote: > On 2/14/06, Adam Olsen <rhamph at gmail.com> wrote: > > In 3.0 it changes to: > > "It's...".encode('utf-8') > > u"It's...".byteencode('utf-8') # Same as above, kept for compatibility > > No. 3.0 won't have "backward compatibility" features. That's the whole > point of 3.0. Conceded. > > I realize it would be odd for the interactive interpret to print them > > as a list of ints by default: > > >>> u"It's...".byteencode('utf-8') > > [73, 116, 39, 115, 46, 46, 46] > > No. This prints the repr() which should include the type. bytes([73, > 116, 39, 115, 46, 46, 46]) is the right thing to print here. Typo, sorry :) -- Adam Olsen, aka Rhamphoryncus
- 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 ]
More information about the Python-Dev mailing list