RetroSearch Browse

Thu Jan 9 13:55:35 CET 2014 · https://mail.python.org/pipermail/python-dev/2014-January/131094.html

> -----Original Message-----
> From: Python-Dev [mailto:python-dev-
> bounces+kristjan=ccpgames.com at python.org] On Behalf Of Antoine Pitrou
> Sent: 9. janúar 2014 12:42
> To: python-dev at python.org
> Subject: Re: [Python-Dev] Python3 "complexity"
> 
> On Thu, 9 Jan 2014 10:15:08 +0000
> Kristján Valur Jónsson <kristjan at ccpgames.com> wrote:
> >
> > Moving to python 3, I found that this quickly caused problems.  So, I
> > explicitly added an encoding.  Better guess an encoding, something that is
> likely, e.g. cp1252 with open(fn1, encoding='cp1252') as f1:
> >     with open(fn2, 'w', encoding='cp1252') as f2:
> >         f2.write(process_text(f1.read())
> 
> If you don't "care" about the encoding, why don't you use latin1?
> Things will roundtrip fine and work as well as under Python 2.

Because latin1 does not define all code points, giving you errors there.  Same with cp1252.
Which is why you need 'surrogateescape' in addition.

K

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2014-January/131094.html below:

[Python-Dev] Python3 "complexity"