All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] python-six: put python2/3 variant together
Date: Tue, 21 May 2019 18:49:35 -0700	[thread overview]
Message-ID: <CAMKF1srz+_Tk5=GNWzBLpNRXoqdCYOmLyNm6XKkFJQFvGcpX=Q@mail.gmail.com> (raw)
In-Reply-To: <1cee8ee543463712e25b4ea4450fb40242a9e84e.camel@linuxfoundation.org>

On Tue, May 21, 2019 at 2:44 PM <richard.purdie@linuxfoundation.org> wrote:
>
> On Tue, 2019-05-21 at 22:59 +0200, Andreas Müller wrote:
> > On Tue, May 21, 2019 at 8:38 PM <richard.purdie@linuxfoundation.org>
> > wrote:
> > > > No sorry mozjs uses old crap in their configurations scripts
> > > > nobody
> > > > else does (python which) and ask for python2 explicitly.
> > >
> > > I've been giving this a bit more thought and its our intent to try
> > > and
> > > remove python2 from OE-Core entirely so adding py2 modules back
> > > seems
> > > like a backwards step.
> > >
> > > I think this will therefore need to go to one of the other layers,
> > > painful as that might be from an include perspective.
> > Yeah a new burden out of thin air is born. You know what I do: Create
> > my own layers and am happy as I am with my other layers.
> >
> > Bye
>
> Its not "out of thin air". It was discussed over two years ago when we
> started a plan of trying to remove python2 dependencies:
>
> http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=1fc2c9315faf65ea05fecf81450dd40b9a330435
>
> This was in line with what upstream python recommended. Upstream python
> has made a clear statement on this too:
>
> https://python3statement.org/
>
> For a release that will ship 3 months before that deadline, it seems
> unreasonable to add this back to oe-core, no?
>

the EOL is expected to be Jan 2020, lets see what happens but I think
it would be good for us
to first switch default python to be python3 and then remove python2
completely IMO, I do not
see any major distro planning to drop py2 at the stroke of it going
EOL as of now, situation might
change in coming months but many of them haven't even switched defaults.

Its good that project is taking lead here but we might leave many users behind.

> Cheers,
>
> Richard
>
>
>
>
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core


  reply	other threads:[~2019-05-22  1:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-21  9:00 [PATCH 1/2] gsettings-desktop-schemas: upgrade 3.28.1 -> 3.32.0 Andreas Müller
2019-05-21  9:00 ` [PATCH 2/2] python-six: put python2/3 variant together Andreas Müller
2019-05-21 16:41   ` Richard Purdie
2019-05-21 18:00     ` Andreas Müller
2019-05-21 18:38       ` richard.purdie
2019-05-21 20:59         ` Andreas Müller
2019-05-21 21:44           ` richard.purdie
2019-05-22  1:49             ` Khem Raj [this message]
2019-05-22 11:05               ` richard.purdie
2019-05-22 11:26                 ` Alexander Kanavin
2019-05-22 14:01                   ` Tim Orling
2019-05-22 16:44                     ` Alejandro Hernandez
2019-05-22  1:55     ` Philip Balister

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='CAMKF1srz+_Tk5=GNWzBLpNRXoqdCYOmLyNm6XKkFJQFvGcpX=Q@mail.gmail.com' \
    --to=raj.khem@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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.