From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] soletta: new package
Date: Sun, 18 Dec 2016 16:10:42 +0100 [thread overview]
Message-ID: <20161218161042.2e2f9975@free-electrons.com> (raw)
In-Reply-To: <CAPi7W80AjNfZOniKchD1MNULFyiwKNDrxNB5bbCtwy9Nx=995w@mail.gmail.com>
Hello,
On Sun, 18 Dec 2016 15:40:09 +0100, Fabrice Fontaine wrote:
> I tried to migrate the python3 scripts to python2 but I will stop. There is
> too many impacts which will not be easily upstreamable (shutil.which must
> replaced by shutilwhich backport, access to tuple attributes is allowed
> only through integers, f.write takes only one argument, configparser has to
> be replaced by ConfigParser which does not support reading configuration
> from a string, ...)
OK, so please keep your original solution then. It's a bit nasty as it
adds python3 to the target (which we don't need), but I don't really see
how do it differently for the moment.
I think it's something we should write as a topic to discuss for the
next Buildroot Developers meeting at FOSDEM.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-12-18 15:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 18:25 [Buildroot] [PATCH 1/2] python-jsonschema: new package Fabrice Fontaine
2016-10-25 18:25 ` [Buildroot] [PATCH 2/2] soletta: " Fabrice Fontaine
2016-12-17 22:52 ` Thomas Petazzoni
[not found] ` <CAPi7W81=a+pP_3X3yfg=uZ+65SDpvpVy3M_2wwAFVchfLSFHCA@mail.gmail.com>
2016-12-18 10:16 ` Thomas Petazzoni
2016-12-18 14:40 ` Fabrice Fontaine
2016-12-18 15:10 ` Thomas Petazzoni [this message]
2016-10-29 14:02 ` [Buildroot] [PATCH 1/2] python-jsonschema: " Thomas Petazzoni
2016-10-29 14:54 ` Fabrice Fontaine
2016-12-17 22:50 ` 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=20161218161042.2e2f9975@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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