On Fri, Jan 17, 2020 at 9:21 PM Denys Dmytriyenko <denis@...> wrote:
On Fri, Jan 17, 2020 at 09:15:09PM +0100, Andreas M?ller wrote:
On Fri, Jan 17, 2020 at 7:35 PM Khem Raj <raj.khem@...> wrote:What, not calling it the worst patch of the year? And the year's just
Just a question: What is the plan with all those recipes which are
On 1/17/20 6:16 AM, Ross Burton wrote:
Python 2 ceased being maintained on the 1st January 2020. We've alreadyperhaps add them to meta-py2 first before this lands
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
- The classes pythonnative, pythondir, distutils, setuptools
going to fail (most headaches I have with old waf): Will meta-oe /
meta-networking..., depend on meta-py2 or kick them out or?
1. Would you accept an apologize for that one?
2. I did not ask for stopping this - just asked how to continue and I
did that for certain reasons: For example: Few minutes ago we saw a
series for npm rework on oe-core. Unfortunately npm as is requires
python2 and many modules. Or the waf stuff: That means somebody has go
to all the projects and ask them for waf upgrade or prepare patches
there (and that means not just upgrading waf). So again: How do we
handle/get rid recipes requiring python2 to build?