<div><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Nov 18, 2019 at 1:05 PM Adrian Bunk <<a href="mailto:bunk@stusta.de">bunk@stusta.de</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 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>
</blockquote><div dir="auto"><br></div><div dir="auto">And why should OE ship something that’s dropped by its own upstream and other distributions </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>
cu<br>
Adrian<br>
<br>
[1] it is not clear whether the Python2 removal in Ubuntu<br>
will be finished in time for 20.04<br>
</blockquote></div></div>