Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #81102 > unrolled thread

Re: python 2.7 and unicode (one more time)

Started byIan Kelly <ian.g.kelly@gmail.com>
First post2014-11-20 11:09 -0700
Last post2014-11-20 11:09 -0700
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.


Contents

  Re: python 2.7 and unicode (one more time) Ian Kelly <ian.g.kelly@gmail.com> - 2014-11-20 11:09 -0700

#81102 — Re: python 2.7 and unicode (one more time)

FromIan Kelly <ian.g.kelly@gmail.com>
Date2014-11-20 11:09 -0700
SubjectRe: python 2.7 and unicode (one more time)
Message-ID<mailman.16039.1416507018.18130.python-list@python.org>
On Thu, Nov 20, 2014 at 11:06 AM, Ian Kelly <ian.g.kelly@gmail.com> wrote:
> On Thu, Nov 20, 2014 at 10:42 AM,  <random832@fastmail.us> wrote:
>> and it means you can't safely
>> blindly use %s with an unknown object.
>
> You can't safely do this anyway. Whether it's %s with a str and a
> unicode, or %s with a unicode and a str, *something* is going to have
> to be implicitly encoded or decoded, and if ascii doesn't happen to be
> the correct encoding then the result will be either an error or a
> silent failure.

Also note that if you use %r instead of %s, you'll get the result you
want (although the unicode string will be quoted rather than encoded).

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web