Re: Portable code: 'from future import unicode_literals' a good idea?

Newsgroups	comp.lang.python
Date	2014-12-16 00:19 -0800
References	<85wq5tpe0g.fsf@benfinney.id.au> <CABicbJKZ9XhhXAwQZrHrb8HUa-4QoKf5jT96msNxeuoDbMzVSg@mail.gmail.com> <85oar4pgrn.fsf_-_@benfinney.id.au> <mailman.16990.1418692803.18130.python-list@python.org>
Message-ID	<ad773902-f5b2-49ce-b095-ee175e5fc0bf@googlegroups.com> (permalink)
Subject	Re: Portable code: 'from __future__ import unicode_literals' a good idea?
From	wxjmfauth@gmail.com

Show all headers | View raw

Le mardi 16 décembre 2014 02:20:52 UTC+1, Ned Batchelder a écrit :
> 
> What's wrong with this part of the recommendation?: "or add a u prefix 
> to the text literal."
> 

The u'' trick in Py2 does not work. Generally
speaking, Python and its characters encoding model
has never work correctly and coherently outside
the ascii world, only a mountain of patches and
workarounds.
In Py3 this kind of behaviour just became more
accute with dramatic consequences.

jmf

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

Thread

Re: Portable code: ‘from __future__ import unicode_literals’ a good idea? Ned Batchelder <ned@nedbatchelder.com> - 2014-12-15 20:19 -0500
  Re: Portable code: 'from __future__ import unicode_literals' a good idea? wxjmfauth@gmail.com - 2014-12-16 00:19 -0800

csiph-web