[OE-core] [PATCH 01/13] python: update to 2.7.17

[Tim Orling]

On Mon, Nov 18, 2019 at 3:27 PM Khem Raj <raj.khem at gmail.com> wrote:

> On Mon, Nov 18, 2019 at 2:55 PM Adrian Bunk <bunk at stusta.de> wrote:
> >
> > On Mon, Nov 18, 2019 at 02:16:30PM -0800, Khem Raj wrote:
> > > On Mon, Nov 18, 2019 at 2:06 PM Adrian Bunk <bunk at stusta.de> wrote:
> > >
> > > > On Mon, Nov 18, 2019 at 01:39:48PM -0800, Khem Raj wrote:
> > > > > On Mon, Nov 18, 2019 at 1:05 PM Adrian Bunk <bunk at stusta.de>
> wrote:
> > > > > > On Mon, Nov 18, 2019 at 10:13:05AM -0800, Khem Raj wrote:
> > > > > > > On Mon, Nov 18, 2019 at 5:08 AM Alexander Kanavin
> > > > > > > <alex.kanavin at gmail.com> wrote:
> > > > > > > >
> > > > > > > > Drop backports, rebase a couple of patches.
> > > > > > > >
> > > > > > > > This is the second last release of py 2.x; upstream support
> ends on
> > > > > > > > 1 January 2020, there will be one final 2.x afterwards.
> > > > > > > >
> > > > > > > > Note that the only thing that still needs python 2.x in
> oe-core is
> > > > > > > > u-boot; when the next u-boot update arrives, we should find
> out
> > > > > > > > where the py3 migration is for that component before merging
> the
> > > > > > > > update.
> > > > > > >
> > > > > > > I guess u-boot need it during build, in that case defer it to
> user to
> > > > > > > have python2 on build host
> > > > > > > could be possible.
> > > > > > >...
> > > > > >
> > > > > > That's a non-option since it could mean
> > > > > > "Yocto 3.1 cannot be built on Ubuntu 20.04".
> > > > > >
> > > > > > Ubuntu 20.04 might end up still shipping Python2,[1]
> > > > > > but you cannot rely on future distributions shipping it.
> > > > >
> > > > > And why should OE ship something that’s dropped by its own
> upstream and
> > > > > other distributions
> > > >
> > > > All I am saying is that relying on the host Python2 is a non-option.
> > > >
> > > > If any layer needs a native Python2, this has to be shipped either in
> > > > this layer or in a layer it depends on.
> > >
> > >
> > > We should explore disabling python support in uboot if it does not
> move to
> > > py3 perhaps there is a way like that having a single recipe require
> py2 is
> > > a bit too much
> >
> > In u-boot build scripts are using Python2.
> >
> > But this is being fixed upstream, so realistically in Yocto 3.1
> > Python2 can move to meta-oe.
>
> No I do not want it in meta-oe, whoever needs it, should step up to
> maintain it and start a new layer
> much like meta-qt4
>

I have the beginnings of scripts to generate a meta-python2 layer. Someone
with a vested interest in keeping python2 supported will need to step up to
maintain it. After bitbake and Oe-core moved to python3, my use of python2
has gone to near zero.

I intend to move all python2 recipes from meta-python to the new layer.
meta-python will become python3 only in 3.1 release timeframe. The bb files
and inc files will also be merged, simplifying AUH and devtool usage.

Attempts to send python2 patches to meta-python after that shift will be
nacked.


> >
> > cu
> > Adrian
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20191118/0c55c9bd/attachment-0001.html>