From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/python3-setuptools: new package
Date: Mon, 31 Dec 2018 15:35:05 +0100 [thread overview]
Message-ID: <20181231153505.62460694@windsurf> (raw)
In-Reply-To: <CALFsTFUXOqqGEUfFuT62jD=7xJVCg09wk6BNf0mAi_dFZ+_cGw@mail.gmail.com>
Hello,
+Yegor in Cc.
On Sun, 30 Dec 2018 20:15:17 +0200, Asaf Kahlon wrote:
> I don't heavily use the meson build system, but after looking at the
> history of setup.py in the official repository,
> I found the commit which made the change. At the commit message they
> stated that:
> "This gives us a consistent experience and a simpler setup across all
> operating systems. Setuptools is available everywhere these days."
> The change is relevant since 0.48.
Indeed, upstream commit 86298f2109d215ad6b26d3462af7b685d52d0dd7 drops
the fallback on distutils, and only setuptools is supported now. This
makes my patch series introducing python3-setuptools even more relevant
then. I would like to see a review from Yegor on this series first, as
he has lots of background in the Python integration in Buildroot.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-12-31 14:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-30 6:41 [Buildroot] [PATCH 1/2] package/python3-setuptools: new package james.hilliard1 at gmail.com
2018-12-30 6:41 ` [Buildroot] [PATCH 2/2] package/meson: bump to version 0.49.0 james.hilliard1 at gmail.com
2019-01-01 10:30 ` Thomas Petazzoni
2018-12-30 11:19 ` [Buildroot] [PATCH 1/2] package/python3-setuptools: new package Thomas Petazzoni
2018-12-30 12:10 ` James Hilliard
2018-12-30 13:24 ` Thomas Petazzoni
2018-12-30 18:15 ` Asaf Kahlon
2018-12-31 14:35 ` 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=20181231153505.62460694@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