From: Adrian Bunk <bunk@stusta.de>
To: Tom Rini <trini@konsulko.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>,
openembedded-architecture
<openembedded-architecture@lists.openembedded.org>
Subject: Re: OE-Core python minimum version requirement
Date: Thu, 5 Dec 2019 01:23:24 +0200 [thread overview]
Message-ID: <20191204232324.GA24229@localhost> (raw)
In-Reply-To: <20191204230237.GE9549@bill-the-cat>
On Wed, Dec 04, 2019 at 06:02:37PM -0500, Tom Rini wrote:
> On Wed, Dec 04, 2019 at 05:45:03PM +0000, Richard Purdie wrote:
>
> > I just enabled hashequiv's server in local mode by default in poky.
> >
> > This causes an unintended side effect of requiring python 3.5 as the
> > minimum version.
> >
> > We had thought that the servers would be 'rare' and a 3.5 version
> > requirement for that was fine. It turns out a local server is also
> > extremely useful.
> >
> > The code needed the python 3.5 async support and trying to write it any
> > other way is a nightmare, we need that performance for the server.
> >
> > At this point I think we just give in and require python 3.5 as a
> > minimum. Any objections?
>
> In having to pick a minimum Python 3 for U-Boot, it was noted that
> Debian/Stretch is 3.4 and gets end of long term support in 2022. 3.5
> was otherwise fine I believe in the end.
Debian 9 (stretch) has 3.5
Debian 8 (jessie) has 3.4
> Tom
cu
Adrian
next prev parent reply other threads:[~2019-12-04 23:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 17:45 OE-Core python minimum version requirement Richard Purdie
2019-12-04 19:07 ` Mark Hatle
2019-12-04 21:07 ` Josef Holzmayr
2019-12-04 23:02 ` Tom Rini
2019-12-04 23:23 ` Adrian Bunk [this message]
2019-12-04 23:26 ` Tom Rini
2019-12-05 2:08 ` [Openembedded-architecture] " Paul Eggleton
2019-12-05 3:10 ` Khem Raj
2019-12-05 6:48 ` Nicolas Dechesne
2019-12-05 8:09 ` Paul Eggleton
2019-12-05 14:37 ` Khem Raj
2019-12-05 16:35 ` Nicolas Dechesne
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=20191204232324.GA24229@localhost \
--to=bunk@stusta.de \
--cc=openembedded-architecture@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=trini@konsulko.com \
/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.