From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] What do we want to do with Python2?
Date: Sun, 12 Jan 2020 21:08:49 +0100 [thread overview]
Message-ID: <20200112210849.0e300c45@windsurf> (raw)
In-Reply-To: <CALFsTFUYfPhOaJTei-sGrbNNY1WBP1TG55UyZywPys_3R3E=Kw@mail.gmail.com>
Hello Asaf,
On Sun, 12 Jan 2020 21:15:12 +0200
Asaf Kahlon <asafka7@gmail.com> wrote:
> As we all know, from the beginning of this year, Python2 is not
> officially maintained anymore.
> In addition, some major python packages started to drop support for
> Python2 recently. One example is the latest setuptools release
> (45.0.0) which added 'python_requires` validation for Python 3.5 or
> later.
>
> Do we have any plan for removing Python2 support in Buildroot? If so,
> do we know for which version we want it to be relevant?
> Of course, I'll be more than happy to help with the process.
An effort was started by Titouan during the last Buildroot Developers
Meeting, and the first step he started with is to ensure that all
packages in Buildroot can work with Python 3.x, which is not yet the
case. Titouan has a status page at
https://elinux.org/Buildroot:Python2Packages. I'm sure you can
participate to that effort, just make sure to sync with Titouan (he is
on IRC, so it's easy to sync if needed).
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-01-12 20:08 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 [this message]
2020-01-13 10:03 ` Titouan Christophe
2020-01-13 10:46 ` 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=20200112210849.0e300c45@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 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.