Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #63300
| Date | 2014-01-06 08:23 -0800 |
|---|---|
| From | Ethan Furman <ethan@stoneleaf.us> |
| Subject | Re: "More About Unicode in Python 2 and 3" |
| References | <lablra$1mc$2@ger.gmane.org> <52C9FD02.3080109@stoneleaf.us> <CAGGBd_qBA0OBELxgzERO4Tfs6quK7oYq8v_2idA=K2ycoiO6Dg@mail.gmail.com> <52CAC780.1010204@stoneleaf.us> <CAPTjJmpB7H2g8PAyf7dYwTinHTPJrX+wh2aWeP8z13ToDbS_Xw@mail.gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.5030.1389027106.18130.python-list@python.org> (permalink) |
On 01/06/2014 07:46 AM, Chris Angelico wrote: > > None of this changes the fact that there are bytes used to > store/transmit stuff, and abstract concepts used to manipulate them. > Just like nobody expects to be able to write a dict to a file without > some form of encoding (pickle, JSON, whatever), you shouldn't expect > to write a character string without first turning it into bytes. Writing is only half the battle, and not, as it happens, where I experience the pain. This data must also be /read/. It has been stated many times that the Py2 str became the Py3 bytes, and yet never in Py2 did 'abc'[1] return 98. -- ~Ethan~
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: "More About Unicode in Python 2 and 3" Ethan Furman <ethan@stoneleaf.us> - 2014-01-06 08:23 -0800
csiph-web