Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] What do we want to do with Python2?
Date: Mon, 13 Jan 2020 11:46:18 +0100	[thread overview]
Message-ID: <20200113114618.6f2480e3@windsurf> (raw)
In-Reply-To: <f0badb1d-2bf7-fb3b-6564-65f1f8c6a4b0@railnova.eu>

On Mon, 13 Jan 2020 11:03:26 +0100
Titouan Christophe <titouan.christophe@railnova.eu> wrote:

> I did not had so much time to continue on the Py2 deprecation track 
> since the ELCE developer meeting, but I intend to continue at the next 
> one (FOSDEM).
> 
> In my opinion, we should strive for a Python3 only Buildroot for the 
> 2021.02 release, and use the year 2020 to either remove Py2-only 
> packages, or wait for an upstream update. I would like to prioritize the 
> packages that use Python at compile time, because that would allow us to 
> get rid of host-python2 first (maybe even for the 2020.05 ?).

Unfortunately, you can't get rid of host-python2 if you still have
python2 available as a target package, because building the target
Python interpreter requires having the matching host Python interpreter
available.

Best regards,

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

      reply	other threads:[~2020-01-13 10:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-12 19:15 [Buildroot] What do we want to do with Python2? Asaf Kahlon
2020-01-12 20:08 ` Thomas Petazzoni
2020-01-13 10:03   ` Titouan Christophe
2020-01-13 10:46     ` Thomas Petazzoni [this message]

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=20200113114618.6f2480e3@windsurf \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox