<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<div class="moz-cite-prefix">On 5/22/2019 7:01 AM, Tim Orling wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CANx9H-D0E+ixNv3Tj4ZBir3Z8xv0=G_1nkufvML7CwA=4RigZw@mail.gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div><br>
</div>
<div><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, May 22, 2019 at 4:27
AM Alexander Kanavin <<a
href="mailto:alex.kanavin@gmail.com"
moz-do-not-send="true">alex.kanavin@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, 22
May 2019 at 13:05, <<a
href="mailto:richard.purdie@linuxfoundation.org"
target="_blank" moz-do-not-send="true">richard.purdie@linuxfoundation.org</a>>
wrote:<br>
<br>
> I don't think we need to switch our default, just be
able to build say<br>
> oe-core without python/python2 in HOSTTOOLS and without
needing python<br>
> 2.7 in OE-Core either.<br>
><br>
> > Its good that project is taking lead here but we
might leave many<br>
> > users behind.<br>
><br>
> I suspect python2 will end up in a layer of its down
which I'm fine<br>
> with, dependencies can then be clearly seen.<br>
<br>
For what it's worth, Fedora is getting serious about Python
2 removal,<br>
and they have a plan for it:<br>
<a
href="https://fedoraproject.org/wiki/Changes/RetirePython2"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://fedoraproject.org/wiki/Changes/RetirePython2</a><br>
<br>
"All packages in Fedora that need Python 2 to run will be
removed from<br>
Fedora 32 regardless of their dependencies. All packages in
Fedora<br>
that need Python 2 to build will be removed from Fedora 32
regardless<br>
of their dependencies. "<br>
</blockquote>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">We have discussed moving meta-python to its
own repository (not under meta-openembedded). As part of
that move, I am proposing the existing python2 recipes move
to a separate (deprecated) layer, as RP mentioned earlier.
Then meta-python will become python3 only. We will also move
recipetool/devtool to provide python3 (only) support. People
that need python2 will very soon have to live with older
stable branches. This should not be a surprise.</div>
<div dir="auto"><br>
</div>
<div dir="auto">We also need to do whatever we can with
upstream projects that are not feeling an urgency to move to
python3. They should likewise not be surprised at the need
to switch.</div>
</div>
</div>
</blockquote>
<p><br>
</p>
<p>I would agree with this as well.</p>
<p><br>
</p>
<p>Cheers,</p>
<p>Alejandro<br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:CANx9H-D0E+ixNv3Tj4ZBir3Z8xv0=G_1nkufvML7CwA=4RigZw@mail.gmail.com">
<div>
<div class="gmail_quote">
<div dir="auto"><br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Alex<br>
-- <br>
_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org"
target="_blank" moz-do-not-send="true">Openembedded-core@lists.openembedded.org</a><br>
<a
href="http://lists.openembedded.org/mailman/listinfo/openembedded-core"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br>
</blockquote>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
</blockquote>
</body>
</html>