<div><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Nov 18, 2019 at 3:27 PM Khem Raj <<a href="mailto:raj.khem@gmail.com">raj.khem@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Mon, Nov 18, 2019 at 2:55 PM Adrian Bunk <<a href="mailto:bunk@stusta.de" target="_blank">bunk@stusta.de</a>> wrote:<br>
><br>
> On Mon, Nov 18, 2019 at 02:16:30PM -0800, Khem Raj wrote:<br>
> > On Mon, Nov 18, 2019 at 2:06 PM Adrian Bunk <<a href="mailto:bunk@stusta.de" target="_blank">bunk@stusta.de</a>> wrote:<br>
> ><br>
> > > On Mon, Nov 18, 2019 at 01:39:48PM -0800, Khem Raj wrote:<br>
> > > > On Mon, Nov 18, 2019 at 1:05 PM Adrian Bunk <<a href="mailto:bunk@stusta.de" target="_blank">bunk@stusta.de</a>> wrote:<br>
> > > > > On Mon, Nov 18, 2019 at 10:13:05AM -0800, Khem Raj wrote:<br>
> > > > > > On Mon, Nov 18, 2019 at 5:08 AM Alexander Kanavin<br>
> > > > > > <<a href="mailto:alex.kanavin@gmail.com" target="_blank">alex.kanavin@gmail.com</a>> wrote:<br>
> > > > > > ><br>
> > > > > > > Drop backports, rebase a couple of patches.<br>
> > > > > > ><br>
> > > > > > > This is the second last release of py 2.x; upstream support ends on<br>
> > > > > > > 1 January 2020, there will be one final 2.x afterwards.<br>
> > > > > > ><br>
> > > > > > > Note that the only thing that still needs python 2.x in oe-core is<br>
> > > > > > > u-boot; when the next u-boot update arrives, we should find out<br>
> > > > > > > where the py3 migration is for that component before merging the<br>
> > > > > > > update.<br>
> > > > > ><br>
> > > > > > I guess u-boot need it during build, in that case defer it to user to<br>
> > > > > > have python2 on build host<br>
> > > > > > could be possible.<br>
> > > > > >...<br>
> > > > ><br>
> > > > > That's a non-option since it could mean<br>
> > > > > "Yocto 3.1 cannot be built on Ubuntu 20.04".<br>
> > > > ><br>
> > > > > Ubuntu 20.04 might end up still shipping Python2,[1]<br>
> > > > > but you cannot rely on future distributions shipping it.<br>
> > > ><br>
> > > > And why should OE ship something that’s dropped by its own upstream and<br>
> > > > other distributions<br>
> > ><br>
> > > All I am saying is that relying on the host Python2 is a non-option.<br>
> > ><br>
> > > If any layer needs a native Python2, this has to be shipped either in<br>
> > > this layer or in a layer it depends on.<br>
> ><br>
> ><br>
> > We should explore disabling python support in uboot if it does not move to<br>
> > py3 perhaps there is a way like that having a single recipe require py2 is<br>
> > a bit too much<br>
><br>
> In u-boot build scripts are using Python2.<br>
><br>
> But this is being fixed upstream, so realistically in Yocto 3.1<br>
> Python2 can move to meta-oe.<br>
<br>
No I do not want it in meta-oe, whoever needs it, should step up to<br>
maintain it and start a new layer<br>
much like meta-qt4<br>
</blockquote><div dir="auto"><br></div><div dir="auto">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.</div><div dir="auto"><br></div><div dir="auto">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.</div><div dir="auto"><br></div><div dir="auto">Attempts to send python2 patches to meta-python after that shift will be nacked.</div><div dir="auto"><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
><br>
> cu<br>
> Adrian<br>
-- <br>
_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org" target="_blank">Openembedded-core@lists.openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" rel="noreferrer" target="_blank">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br>
</blockquote></div></div>