public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot-Custodians]  [RFC] Minimum Python 3 version?
Date: Fri, 27 Sep 2019 14:57:33 -0700	[thread overview]
Message-ID: <87sgohe71u.fsf@yucca> (raw)
In-Reply-To: <4f2ed2e7-1b95-d917-0a28-32037bd271cd@gmx.de>

On 2019-09-27, Heinrich Schuchardt wrote:
> On 9/27/19 6:36 PM, Peter Robinson wrote:
>>> 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.
...
>>> 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?
>>
>> That makes sense to me, the el8 distros (RHEL, CentOS etc) have 3.6
>> and el7 has 3.6 available by means, Fedora is at least 3.6 everywhere
>> for current releases so I don't think we should have any issues.
>
> Debian Stretch has Python 3.4.2.
> End of life in 2020, end of long term support in 2022
>
> Debian Buster has Python 3.7.3
> End of life in 2022.
>
> I would not expect expect Debian Stretch moving to current U-Boot. So
> requiring Python 3.6 to build current U-Boot seems ok for Debian.

Python 3.6+ seems good to me, yes. Not planning on backporting anything
new to older Debian releases.

Thanks for working on the update to python3!

live well,
  vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190927/5256401c/attachment.sig>

  reply	other threads:[~2019-09-27 21:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-27 16:05 [U-Boot] [RFC] Minimum Python 3 version? Tom Rini
2019-09-27 16:36 ` Peter Robinson
2019-09-27 21:20   ` [U-Boot] [U-Boot-Custodians] " Heinrich Schuchardt
2019-09-27 21:57     ` Vagrant Cascadian [this message]
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=87sgohe71u.fsf@yucca \
    --to=vagrant@debian.org \
    --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