[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190905065701.4744e66a@lwn.net>
Date: Thu, 5 Sep 2019 06:57:01 -0600
From: Jonathan Corbet <corbet@....net>
To: Mauro Carvalho Chehab <mchehab+samsung@...nel.org>
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
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?
Thanks,
jon
Powered by blists - more mailing lists