<div dir="ltr"><div dir="ltr">On Mon, 18 Nov 2019 at 23:06, Adrian Bunk <<a href="mailto:bunk@stusta.de">bunk@stusta.de</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><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></blockquote><div><br></div><div>Sadly, not relying on host Python 2 is not possible. Building Python 2 needs a working binary of Python 2. So there is a circular dependency chain that cannot be broken: host py2 -> native py2 -> target py2 -> self-hosted packagegroup. <br></div><div><br></div><div>You can remove all three versions of py2, but not any of them individually.</div><div><br></div><div>Alex<br></div></div></div>