From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] Minimum Python 3 version?
Date: Fri, 27 Sep 2019 12:05:01 -0400 [thread overview]
Message-ID: <20190927160501.GU11486@bill-the-cat> (raw)
Hey all,
I'm currently kicking test.py to use Python 3 instead of Python 2.7 and
seeing places where it would (seemingly) be nice to be able to say that
we have Python 3.6 as our minimum version. To do this however we'll
have to tell people using older LTS distributions that they need to
figure out the best way for them to install a newer Python is, if they
want to run tests at least.
This will also mean moving GitLab to "bionic" rather than "xenial", but
that's not too bad and I've done so for trying to get all of the fs
tests to run (they don't, but I think that's down to needing to kick
gitlab-runner harder) and also moving Travis-CI to bionic but that too
is now just a few-line change to .travis.yml
So, does anyone object to saying that for everything that uses Python to
work, Python 3.6 or newer is needed, and for more common tools we'll
make best-effort to support older?
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190927/0632d7a2/attachment.sig>
next reply other threads:[~2019-09-27 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 16:05 Tom Rini [this message]
2019-09-27 16:36 ` [U-Boot] [RFC] Minimum Python 3 version? Peter Robinson
2019-09-27 21:20 ` [U-Boot] [U-Boot-Custodians] " Heinrich Schuchardt
2019-09-27 21:57 ` Vagrant Cascadian
2019-10-01 16:32 ` Matthias Brugger
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=20190927160501.GU11486@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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