All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/scons: explicitly specify host Python 3
Date: Tue, 14 Jul 2020 15:51:02 +0200	[thread overview]
Message-ID: <20200714155102.11b379fe@windsurf.home> (raw)
In-Reply-To: <17dc14ac-1f7f-ef67-84af-e41241ffe86a@railnova.eu>

On Tue, 14 Jul 2020 15:31:09 +0200
Titouan Christophe <titouan.christophe@railnova.eu> wrote:

> > HOST_SCONS_NEEDS_HOST_PYTHON = $(if ($(BR2_PACKAGE_PYTHON),python,python3)  
> 
> AFAIK, we usually do the opposite:
> $(if $(BR2_PACKAGE_PYTHON3),python3,python)

Yes, but the idea is to reverse this progressively, and switch more and
more to "Python 3.x" is the default.

> In my very own opinion, we should now only use host-python3 everywhere, 
> unless host-python(2) is strictly required. Pragmatically speaking, in 
> the rare cases where host-python(2) is still necessary, having both 
> Pythons on the host would not be that much of an overhead (both in terms 
> of building time and disk space); and would reduce the clutter in all 
> the places where we do the fancy dance you describe above.

I'm fine with moving towards host-python3 only where possible.

> On the target side, I'm also looking forward to invert the target 
> py2/py3 logic, ie changing
> 
> $(if $(BR2_PACKAGE_PYTHON3),python3,python))
> 
> into
> 
> $(if $(BR2_PACKAGE_PYTHON),python,python3))
> 
> especially in package/pkg-python.mk.
> 
> Again, the goal is to have Python3 as default, while still allowing old 
> Python2-only programs to run where needed. I'll try to find some time 
> this week to go through the Buildroot tree and update the Python3 
> migration page (https://www.elinux.org/Buildroot:Python2Packages), as 
> there has been some change since the FOSDEM dev days. This shall help us 
> understand where Python2 is still required.

That would be great indeed!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-07-14 13:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-14  3:39 [Buildroot] [PATCH] package/scons: explicitly specify host Python 3 Robert Hancock
2020-07-14  8:15 ` Thomas Petazzoni
2020-07-14 13:31   ` Titouan Christophe
2020-07-14 13:51     ` Thomas Petazzoni [this message]
2020-07-14 16:23   ` Robert Hancock
2022-01-08 11:20 ` Thomas Petazzoni

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=20200714155102.11b379fe@windsurf.home \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.