Re: [RFC PATCH] python: remove Python 2 and all supporting classes


Andreas Müller
 

On Sun, Jan 19, 2020 at 2:59 PM Richard Purdie
<richard.purdie@...> wrote:

On Fri, 2020-01-17 at 13:28 -0800, Khem Raj wrote:
On Fri, Jan 17, 2020 at 12:15 PM Andreas Müller <
schnitzeltony@...> wrote:
On Fri, Jan 17, 2020 at 7:35 PM Khem Raj <raj.khem@...>
wrote:
On 1/17/20 6:16 AM, Ross Burton wrote:
Python 2 ceased being maintained on the 1st January
2020. We've already
removed all users of it from oe-core so the final step is to
move the
recipe and supporting classes to meta-python2.

The following are removed in this commit:
- python and python-native 2.7.17
- python-setuptools
- The classes pythonnative, pythondir, distutils, setuptools
perhaps add them to meta-py2 first before this lands
Just a question: What is the plan with all those recipes which are
going to fail (most headaches I have with old waf): Will meta-oe /
meta-networking..., depend on meta-py2 or kick them out or?
I am a bit apprehensive about creating direct dependency, since
that would prolong the support, so I would still like to use rest of
this
dev cycle to fix as many recipes as we can to not depend on py2
and I will publish the failing recipes, so far we have had no failure
run for all meta-openembedded layers on master. In the end perhaps
we will be able to blacklist the recipes which still need py2 and are
not
migrarted to py3, or if we end up with a lot of critical ones then
we might want to create dep on meta-py2, hope that clarifies my
thoughts
on course of action.

but I am sure, if you have needs for py2 then including meta-py2 will
be the place to go and I hope that it will provide the existing
functionality that's being pushed out from the core.
I have to admit I don't know what the best solution for meta-oe is.

If py2 pieces are left in meta-openembedded, it may be best to move
them to a separate sublayer to make the issue clearer?

FWIW I did remove some python binding pieces in meta-gplv2 to work
around problems, a similar strategy may work for some things too?

I have however merged the patch for OE-Core. The reasons:

* We've known this was coming for some time
* OE-Core is due to build M2 this week
* The change has long been scheduled for M2
* Its a forcing function, we are going to have to deal with this
* This gives meta-oe time to resolve the issues before April

Sorry Khem!
To avoid double efforts: I will start with mozjs now. Did work on that
already and tried to build it from firefox-esr V68.xx. That did not
work because:

* We nee meta-rust for that
* Python scripts were not upgraded to python3 (because the moved to cargo/rust)

Hope to get it working soon...

Andreas

Cheers,

Richard


Join yocto@lists.yoctoproject.org to automatically receive all group messages.