Re: [PATCH 01/13] python: update to 2.7.17

[Adrian Bunk <bunk@stusta.de>]

On Tue, Nov 19, 2019 at 12:30:41PM +0100, Alexander Kanavin wrote:
> On Tue, 19 Nov 2019 at 08:58, Tim Orling <ticotimo@gmail.com> wrote:
> 
> > 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.
> >
> > 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.
> >
> > Attempts to send python2 patches to meta-python after that shift will be
> > nacked.
> 
> 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:
> https://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-extended/mozjs/mozjs_60.5.2.bb
> 
> It's tempting to force the transition by breaking things, but it also
> antagonizes users.

The problem is not that half of meta-oe would fail, but the few hard cases.

There might be 1 or 2 recipes where the rational solution would be to 
keep Python 2 in meta-oe for one release until a new upstream of these 
recipes solves the problem.

AFAIK for nodejs the choice for Yocto 3.1 will be between a short-term 
stable that can be built with Python 3 but will become EOL shortly after 
Yocto 3.1 releases, and an LTS release with upstream support for 2 more 
years that needs Python 2.

Python 2 is security supportable without upstream support since many
other distributions have committed to do the same, security supporting
Node.js without upstream support might be impossible.

> Alex

cu
Adrian