[oe] ANNOUNCEMENT: meta-python2 has been created

[Tim Orling]

On Mon, Dec 2, 2019 at 1:49 PM akuster808 <akuster808 at gmail.com> wrote:

> Tim,
>
> On 12/2/19 7:56 AM, Tim Orling wrote:
> > Why?
> > ====
> > With the pending EOL (end-of-life) of Python 2 in a month [1], it is time
> > to move python2 recipes to a new home. For that reason, meta-python2 [2]
> > has been created as the home for legacy python2 recipes.
>
> Thanks for putting in the time to get this sorted out.
>

It was a slog, but it was worth it. You are welcome :)

>
> > How?
> > ====
> > It was a design goal to keep the original history of meta-python, but
> only
> > the python2 parts. In order to accomplish this git-filter-repo was used
> > [3]. The exact steps used can be seen in a gist [4]. After that script
> was
> > run, manual merging of *.inc and *.bb files was performed to make recipe
> > maintenance with AUH (auto upgrade helper) and devtool easier. Since this
> > layer does not have to support two python versions, the reason for the
> *.bb
> > and *.inc split has been eliminated. Commits that upgraded recipes to
> > python2-incompatible versions were reverted. Changes to make the recipes
> > build and ptests be runnable were also made (to master branch). The
> stable
> > branches were also kept, to make it easier to refer back to prior history
> > and allow developers to use meta-python2 only in their workflow. NOTE:
> The
> > stable branches may require work to make them usable, this was outside
> the
> > scope of the immediate effort.
>
>
> Should we have a separate patch work for this layer?
>
>
As I understand it, that requires a separate mailing list, which currently
feels like undo overhead. But I would love a separate patchwork instance.

If the normal Stable branch format is used for patches, it should be
> easy to sort out so we can see how it goes and make adjustments as we go.
>
> The volume for stable meta-python patches tends to be low so I don't
> mind sorting things out from master to zeus between the two branches.
>
> There are a few changes I would like to make to the zeus branch of
meta-python2 (clean up of packagegroup-meta-python2 and such), but I agree
that the amount of patches tends to be low and it is not that much of a
burden. It certainly seems worth supporting zeus, as I had originally
intended meta-python2 to exist before the zeus release. It is also worth
considering warrior. Much further back than that I would want to hear from
users that want to step up to help maintain the older stable releases. It
is certainly doable to perform builds on gitlab-ci for as far back as 'kas'
supports releases (which as I recall is krogoth and morty believe it or
not).

>
> - armin
> >
> > What next?
> > =========
> > Python2 recipes from meta-python will be dropped via patches sent to the
> > mailing list. Python2 recipes from meta-oe and meta-networking, which
> have
> > already been added to meta-python2, will be dropped via patches to the
> > mailing list. Other layers are welcome to do the same.
> >
> > Recipe upgrades to meta-python2 will also be coming, for instance Django
> > 1.11.x LTS is the last version to support Python 2, but we are not at the
> > latest release of that series.
> >
> > The original meta-python will become Python3-only and patches for python2
> > support will be nacked and redirected to meta-python2.
> >
> > python2 itself will likely be moved from oe-core into meta-python2
> >
> > [1] https://www.python.org/doc/sunset-python-2/
> > [2] https://git.openembedded.org/meta-python2/
> > [3] https://github.com/newren/git-filter-repo
> > [4] https://gist.github.com/moto-timo/ab70ab96ddbaf5fd1226bd21dbbfec9b
>
>
>