From: Stephen Hemminger <stephen@networkplumber.org>
To: Owen Hilyard <ohilyard@iol.unh.edu>
Cc: dts@dpdk.org, dev <dev@dpdk.org>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Subject: Re: [RFC] Python Version for DTS
Date: Thu, 20 Jan 2022 07:53:24 -0800 [thread overview]
Message-ID: <20220120075324.04a53563@hermes.local> (raw)
In-Reply-To: <CAHx6DYD-=b0yyBPDTbufon5SYLdOrBaopV+eTkkw6yEHy7-vpw@mail.gmail.com>
On Thu, 20 Jan 2022 09:42:51 -0500
Owen Hilyard <ohilyard@iol.unh.edu> wrote:
> Hello Everyone,
>
> DTS has operated using the version of python available in the oldest
> supported Ubuntu LTS for a while now, but after some discussion in the
> working group, we decided that DTS should designate a Python version
> explicitly for the sake of compatibility. My initial proposal is Python
> 3.6, due to Ubuntu 18.04 LTS shipping with it by default. Currently, the
> Community CI Lab runs Python 3.8 on all testers (Ubuntu 20.04 LTS), but for
> the sake of compatibility a lower python version might be desirable.
>
> The working group is specifically looking for reasons to not use Python 3.6.
>
> The Community CI Lab perspective is that versions higher than 3.8 are not
> acceptable due to the issues with changing the default Python installation
> on Ubuntu. This may be raised to 3.10 in June of this year after we have
> had time to evaluate the 22.04 release of Ubuntu.
>
> Owen Hilyard
Python 3.6 reached end of life in 2021.
https://lwn.net/Articles/880859/
next prev parent reply other threads:[~2022-01-20 15:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 14:42 [RFC] Python Version for DTS Owen Hilyard
2022-01-20 15:53 ` Stephen Hemminger [this message]
2022-01-21 1:00 ` Honnappa Nagarahalli
2022-02-02 13:37 ` Owen Hilyard
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=20220120075324.04a53563@hermes.local \
--to=stephen@networkplumber.org \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=dts@dpdk.org \
--cc=ohilyard@iol.unh.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.