Re: python 2.7 and unicode (one more time)

From	Mark Lawrence <breamoreboy@yahoo.co.uk>
Subject	Re: python 2.7 and unicode (one more time)
Date	2014-11-20 20:59 +0000
References	(1 earlier) <m4kn66$ma3$1@ger.gmane.org> <1416491999.209592.193345213.3A6FF9A4@webmail.messagingengine.com> <CAPTjJmr5NWMFCfU8jaNd2g2f9cQ1y+zO3qT7yVcC_m9vKXN6fw@mail.gmail.com> <1416505379.268157.193439717.66E319D4@webmail.messagingengine.com> <CALwzid=qc66rGfr2nVM19bK3GfNQ4PUj2=3nzp0bEGzfW--1CA@mail.gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.16054.1416517215.18130.python-list@python.org> (permalink)

Show all headers | View raw

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

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: python 2.7 and unicode (one more time) Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-11-20 20:59 +0000

csiph-web