<div><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Nov 19, 2019 at 8:30 AM 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 Tue, Nov 19, 2019 at 07:49:15AM -0800, Khem Raj wrote:<br>
> On Tue, Nov 19, 2019 at 3:30 AM Alexander Kanavin<br>
> <<a href="mailto:alex.kanavin@gmail.com" target="_blank">alex.kanavin@gmail.com</a>> wrote:<br>
> ><br>
> > On Tue, 19 Nov 2019 at 08:58, Tim Orling <<a href="mailto:ticotimo@gmail.com" target="_blank">ticotimo@gmail.com</a>> wrote:<br>
> >><br>
> >><br>
> >> 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.<br>
> >><br>
> >> 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.<br>
> >><br>
> >> Attempts to send python2 patches to meta-python after that shift will be nacked.<br>
> ><br>
> ><br>
> > Thanks! There is however a missing part: how close is meta-oe to being py2-free? Oe-core is very close (u-boot is the last holdout as noted), but I am not sure that we can simply take out py2, and not have half of meta-oe fail. For instance (random example) mozjs, a fairly important component, still pulls it in, together with a few 3rd party libraries: <a href="https://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-extended/mozjs/mozjs_60.5.2.bb" rel="noreferrer" target="_blank">https://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-extended/mozjs/mozjs_60.5.2.bb</a><br>
> ><br>
> > It's tempting to force the transition by breaking things, but it also antagonizes users.<br>
> <br>
> Its for how python2 should be organised after it retires and<br>
> suggestion is to move it to an independent layer rather than<br>
> meta-openembedded repo,<br>
> wether, layers under meta-openembedded will depend on it is a separate issue<br>
<br>
You want meta-oe to have a LAYERDEPENDS on a new python2 layer that is <br>
not in meta-openembedded?</blockquote><div dir="auto"><br></div><div dir="auto">Ideally no preferable is that all recipes move to py3 or they perhaps blacklist until someone ports them to py3</div><div dir="auto"><br></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>
</blockquote></div></div>