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


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

Re: python 2.7 and unicode (one more time)

Started byMark Lawrence <breamoreboy@yahoo.co.uk>
First post2014-11-20 20:59 +0000
Last post2014-11-20 20:59 +0000
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) Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-11-20 20:59 +0000

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

FromMark Lawrence <breamoreboy@yahoo.co.uk>
Date2014-11-20 20:59 +0000
SubjectRe: python 2.7 and unicode (one more time)
Message-ID<mailman.16054.1416517215.18130.python-list@python.org>
On 20/11/2014 18:06, Ian Kelly 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.
>

All I know about this encoding/decoding malarky is that I'd prefer an 
error to a silent failure any day of the week.

-- 
My fellow Pythonistas, ask not what our language can do for you, ask
what you can do for our language.

Mark Lawrence

[toc] | [standalone]


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


csiph-web