[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190905162810.2388d532@coco.lan>
Date: Thu, 5 Sep 2019 16:28:10 -0300
From: Mauro Carvalho Chehab <mchehab+samsung@...nel.org>
To: Jonathan Corbet <corbet@....net>
Cc: Linux Media Mailing List <linux-media@...r.kernel.org>,
Mauro Carvalho Chehab <mchehab@...radead.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Joe Perches <joe@...ches.com>, linux-kernel@...r.kernel.org,
Jessica Yu <jeyu@...nel.org>,
Federico Vaga <federico.vaga@...a.pv.it>,
Thomas Gleixner <tglx@...utronix.de>, linux-doc@...r.kernel.org
Subject: Re: [PATCH] docs: license-rules.txt: cover SPDX headers on Python
scripts
Em Thu, 5 Sep 2019 06:57:01 -0600
Jonathan Corbet <corbet@....net> escreveu:
> On Thu, 5 Sep 2019 06:23:13 -0300
> Mauro Carvalho Chehab <mchehab+samsung@...nel.org> wrote:
>
> > Python's PEP-263 [1] dictates that an script that needs to default to
> > UTF-8 encoding has to follow this rule:
> >
> > 'Python will default to ASCII as standard encoding if no other
> > encoding hints are given.
> >
> > To define a source code encoding, a magic comment must be placed
> > into the source files either as first or second line in the file'
>
> So this is only Python 2, right? Python 3 is UTF8 by default. Given that
> Python 2 is EOL in January, is this something we should be concerned
> about? Or should we instead be making sure that all the Python we have
> in-tree works properly with Python 3 and be done with it?
I don't think we can count that python 3 uses utf-8 per default.
I strongly suspect that, if one uses a Python3 version < 3.7, it will
still default to ASCII.
On a quick look, the new UTF-8 mode was added on PEP-540:
https://www.python.org/dev/peps/pep-0540/
Such change happened at Python 3.7.
Yet, according with PEP, it defaults to off, unless when using POSIX
locale.
Thanks,
Mauro
Powered by blists - more mailing lists