On Mon, 18 Nov 2019 at 23:06, Adrian Bunk <[email protected]> wrote: > > > > 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. >
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. You can remove all three versions of py2, but not any of them individually. Alex
-- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
