linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	Joe Perches <joe@perches.com>,
	linux-kernel@vger.kernel.org, Jessica Yu <jeyu@kernel.org>,
	Federico Vaga <federico.vaga@vaga.pv.it>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: license-rules.txt: cover SPDX headers on Python scripts
Date: Thu, 5 Sep 2019 14:10:44 -0300	[thread overview]
Message-ID: <20190905141044.4eb3a622@coco.lan> (raw)
In-Reply-To: <20190905141723.GB25790@kroah.com>

Em Thu, 5 Sep 2019 16:17:23 +0200
Greg Kroah-Hartman <gregkh@linuxfoundation.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@kernel.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

  reply	other threads:[~2019-09-05 17:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190905055614.7958918b@coco.lan>
2019-09-05  9:23 ` [PATCH] docs: license-rules.txt: cover SPDX headers on Python scripts Mauro Carvalho Chehab
2019-09-05  9:27   ` Greg Kroah-Hartman
2019-09-05 10:50     ` Mauro Carvalho Chehab
2019-09-05 11:01       ` [PATCH 1/3] docs: sphinx: add SPDX header for some sphinx extensions Mauro Carvalho Chehab
2019-09-05 12:07     ` [PATCH] docs: license-rules.txt: cover SPDX headers on Python scripts Mauro Carvalho Chehab
2019-09-05 17:45       ` Joe Perches
2019-09-06 11:34         ` Mauro Carvalho Chehab
2019-09-06 11:37           ` Mauro Carvalho Chehab
2019-09-06 12:20           ` Joe Perches
2019-09-06 14:45             ` Mauro Carvalho Chehab
2019-09-06 16:20               ` Joe Perches
2019-09-06 17:33           ` Joe Perches
2019-09-06 18:17             ` Mauro Carvalho Chehab
2019-09-06 18:30               ` Joe Perches
2019-09-06 18:12           ` [RFC PATCH] tools: Add SPDX license to man pages Joe Perches
2019-09-06 19:53             ` Mauro Carvalho Chehab
2019-09-05 12:57   ` [PATCH] docs: license-rules.txt: cover SPDX headers on Python scripts Jonathan Corbet
2019-09-05 14:17     ` Greg Kroah-Hartman
2019-09-05 17:10       ` Mauro Carvalho Chehab [this message]
2019-09-06 16:41       ` Markus Heiser
2019-09-05 19:28     ` Mauro Carvalho Chehab
2019-09-05 19:40       ` Jonathan Corbet
2019-09-05 20:07         ` Mauro Carvalho Chehab
2019-09-06 15:18           ` Markus Heiser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190905141044.4eb3a622@coco.lan \
    --to=mchehab+samsung@kernel.org \
    --cc=corbet@lwn.net \
    --cc=federico.vaga@vaga.pv.it \
    --cc=gregkh@linuxfoundation.org \
    --cc=jeyu@kernel.org \
    --cc=joe@perches.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).