Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #63300 > unrolled thread
| Started by | Ethan Furman <ethan@stoneleaf.us> |
|---|---|
| First post | 2014-01-06 08:23 -0800 |
| Last post | 2014-01-06 08:23 -0800 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: "More About Unicode in Python 2 and 3" Ethan Furman <ethan@stoneleaf.us> - 2014-01-06 08:23 -0800
| From | Ethan Furman <ethan@stoneleaf.us> |
|---|---|
| Date | 2014-01-06 08:23 -0800 |
| Subject | Re: "More About Unicode in Python 2 and 3" |
| Message-ID | <mailman.5030.1389027106.18130.python-list@python.org> |
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 top | Article view | comp.lang.python
csiph-web