From: akuster808 <akuster808@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: moving OpenEmbedded-core to Python 3
Date: Mon, 25 Apr 2016 08:11:03 -0700 [thread overview]
Message-ID: <571E3387.6090201@gmail.com> (raw)
In-Reply-To: <571E0BF3.8080408@linux.intel.com>
On 04/25/2016 05:22 AM, Alexander Kanavin wrote:
> Hello everyone,
>
> we want to deprecate Python 2 in oe-core and set Python 3 as the
> default, preferred choice. What does this mean?
What is the target to make Python3 default, 2.2?
>
> 1) Introducing new Python 2 dependencies via new recipes or additional
> DEPENDS etc. in existing recipes will be discouraged: you'll have to
> provide a reason.
Will there be any kind of QA warning for these dependencies? this will
help scope how many recipes need to be looked at. there are a lot of
layers out there.
>
> 2) Bitbake itself is at the moment Python 2 only - which will be addressed.
What will the env setup script display then?
>
> 3) OE-core recipes that are currently dependent on Python 2 will be
> moved to Python 3 whenever possible (e.g. when nothing in oe-core
> requires them to be built against python 2). This may break some of your
> code, so please do try any patchsets before they land in master (or
> stable release), and suggest alternatives.
>
> 4) Of course, there is a large mass of Python 2 code out there, which
> may never be ported to Python 3, so Python 2 will continue to be
> provided at least until it's no longer supported upstream (the current
> date is 2020).
>
> I'll prepare an initial patchset for review, so please keep an eye on it.
thanks for doing the the initial work.
- armin
>
>
> Thanks,
> Alex
next prev parent reply other threads:[~2016-04-25 15:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 12:22 moving OpenEmbedded-core to Python 3 Alexander Kanavin
2016-04-25 15:11 ` akuster808 [this message]
2016-04-27 12:51 ` Alexander Kanavin
2016-04-29 20:43 ` Khem Raj
2016-05-02 10:14 ` Alexander Kanavin
2016-05-02 21:43 ` Khem Raj
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=571E3387.6090201@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox