From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] support/scripts/check-uniq-files: run with Python 2.6
Date: Tue, 21 Aug 2018 12:14:58 +0200 [thread overview]
Message-ID: <20180821121458.69683413@windsurf> (raw)
In-Reply-To: <33f2f5c9d9cdbb320e52.1532112144@cveaol6qa08.wv.mentorg.com>
Hello Hollis,
On Fri, 20 Jul 2018 11:42:24 -0700, Hollis Blanchard wrote:
> Support Python 2.6 by switching from argparse (introduced in Python 2.7) to
> optparse. Python 2.6 is the version of Python in RHEL6.5.
>
> optparse was deprecated in 2.7, but is still usable, so the script now runs in
> more environments.
>
> Backports of argparse to 2.6 are available, but can be impractical to require
> on all hosts (e.g. hosts belonging to end-users who are unfamiliar with Python
> package management, corporate-managed build hosts where installing packages is
> difficult or impossible).
>
> Signed-off-by: Hollis Blanchard <hollis_blanchard@mentor.com>
We had a bit of discussion about this on IRC today, and both Yann's
feeling and mine is that optparse is long deprecated (since Python
2.7), so it is really annoying to keep using it just for the sake of
Python 2.6 users.
Python 2.6 users can simply install the argparse module as a third
party module, and use Buildroot. I think it's a reasonable trade-off
between using modern APIs and keeping compatibility with older build
systems.
So I've marked this patch as Rejected in patchwork. Sorry :-/
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-08-21 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 18:42 [Buildroot] [PATCH] support/scripts/check-uniq-files: run with Python 2.6 Hollis Blanchard
2018-08-21 10:14 ` 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=20180821121458.69683413@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