From: "Denys Dmytriyenko" <denis@denix.org>
To: "Andreas Müller" <schnitzeltony@gmail.com>
Cc: Khem Raj <raj.khem@gmail.com>, yocto@lists.yoctoproject.org
Subject: Re: [yocto] [RFC PATCH] python: remove Python 2 and all supporting classes
Date: Mon, 20 Jan 2020 13:15:24 -0500 [thread overview]
Message-ID: <20200120181524.GA4735@denix.org> (raw)
In-Reply-To: <CALbNGRTv8S3V9TLE+uwX4Dei=5m1LBKowzGF5Nr1L8iPHBSQsg@mail.gmail.com>
On Fri, Jan 17, 2020 at 09:55:55PM +0100, Andreas Müller wrote:
> On Fri, Jan 17, 2020 at 9:21 PM Denys Dmytriyenko <denis@denix.org> 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@gmail.com> 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?
> >
> > What, not calling it the worst patch of the year? And the year's just
> > started... :)
> Denys
>
> 1. Would you accept an apologize for that one?
Don't worry about that, let's file it under "overreaction due to stress"
category, shall we? :)
> 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?
Yes, all good points. I would agree with Khem - let's drop it and try to
fix as many issues as possible, while we still have time until the release.
Distros can have own dependency on meta-python2, but meta-openembedded and
openembedded-core should not depend on deprecated components, IMHO.
--
Denys
next prev parent reply other threads:[~2020-01-20 18:15 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 14:16 [RFC PATCH] python: remove Python 2 and all supporting classes Ross Burton
2020-01-17 14:16 ` Ross Burton
2020-01-17 16:45 ` [yocto] " Armin Kuster
2020-01-17 16:53 ` Denys Dmytriyenko
2020-01-17 16:53 ` Denys Dmytriyenko
2020-01-17 18:34 ` Khem Raj
2020-01-17 20:15 ` Andreas M?ller
2020-01-17 20:21 ` Denys Dmytriyenko
2020-01-17 20:55 ` Andreas M?ller
2020-01-17 21:08 ` Randy MacLeod
2020-01-20 11:22 ` Ross Burton
2020-01-21 17:09 ` Konrad Weihmann
2020-01-21 17:27 ` Martin Jansa
2020-01-21 17:44 ` Adrian Bunk
2020-01-21 19:40 ` Konrad Weihmann
2020-01-21 22:05 ` Khem Raj
2020-01-20 18:15 ` Denys Dmytriyenko [this message]
2020-01-20 21:57 ` Andreas M?ller
2020-01-17 21:28 ` Khem Raj
2020-01-19 13:59 ` Richard Purdie
2020-01-19 17:05 ` Andreas M?ller
2020-01-19 20:26 ` Randy MacLeod
2020-01-18 8:41 ` Richard Purdie
2020-01-18 8:41 ` [oe] " Richard Purdie
2020-01-19 22:23 ` Andrey Zhizhikin
2020-01-19 22:23 ` [oe] " Andrey Zhizhikin
2020-01-19 22:23 ` Andrey Zhizhikin
2020-01-20 11:24 ` Ross Burton
2020-01-20 11:24 ` [oe] " Ross Burton
2020-01-20 11:24 ` Ross Burton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200120181524.GA4735@denix.org \
--to=denis@denix.org \
--cc=raj.khem@gmail.com \
--cc=schnitzeltony@gmail.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.