Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #81082 > unrolled thread
| Started by | Peter Otten <__peter__@web.de> |
|---|---|
| First post | 2014-11-20 16:40 +0100 |
| Last post | 2014-11-20 16:40 +0100 |
| 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: python 2.7 and unicode (one more time) Peter Otten <__peter__@web.de> - 2014-11-20 16:40 +0100
| From | Peter Otten <__peter__@web.de> |
|---|---|
| Date | 2014-11-20 16:40 +0100 |
| Subject | Re: python 2.7 and unicode (one more time) |
| Message-ID | <mailman.16024.1416498018.18130.python-list@python.org> |
random832@fastmail.us wrote: > On Thu, Nov 20, 2014, at 07:35, Peter Otten wrote: >> >>> "%s nötig %s" % (u"üblich", u"ähnlich") >> Traceback (most recent call last): >> File "<stdin>", line 1, in <module> >> UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 4: >> ordinal not in range(128) > > This is surprising to me - why is it trying to decode the format string, > rather than encode the arguments? Probably to make it easier to mix byte and unicode strings. In hindsight it may not have been a good idea, but it had the potential to save some memory. I think that you may get a Unicode/Encode/Error when you try to /decode/ a unicode string is more confusing...
Back to top | Article view | comp.lang.python
csiph-web