linux-kernel - Re: [PATCH] docs: license-rules.txt: cover SPDX headers on Python scripts

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 5 Sep 2019 14:10:44 -0300
From:   Mauro Carvalho Chehab <mchehab+samsung@...nel.org>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Jonathan Corbet <corbet@....net>,
        Linux Media Mailing List <linux-media@...r.kernel.org>,
        Mauro Carvalho Chehab <mchehab@...radead.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 16:17:23 +0200
Greg Kroah-Hartman <gregkh@...uxfoundation.org> escreveu:

> On Thu, Sep 05, 2019 at 06:57:01AM -0600, Jonathan Corbet wrote:
> > 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? 

Well, Debian 10 (buster) was launched this year, and still comes with python2
(with is the default):

	$ ls -la /usr/bin/python
	lrwxrwxrwx 1 root root 7 Mar  4  2019 /usr/bin/python -> python2

I think Debian devs will keep it maintained for a while, as this is a LTS
distro.

> > 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 recommend just using python 3 everywhere and be done with it as there
> are already many distros that default to that already.

Then we need to change the scripts, as they're currently pointing to
/usr/bin/python instead of /usr/bin/python3. At least on the distros I
use myself, this doesn't point to /etc/alternates. Instead, it is just
an alias to python2.

Thanks,
Mauro