All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Ross Burton <Ross.Burton@arm.com>
Cc: Khem Raj <raj.khem@gmail.com>, Markus Volk <f_l_k@t-online.de>,
	 "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [oe-core][PATCH] python3: add ${bindir}/python symlink
Date: Tue, 22 Nov 2022 19:03:59 +0100	[thread overview]
Message-ID: <CANNYZj9uxKov0vrox7N3kv-HdQJ9VDbLu7Jsn_SuVUTz_Nbrzw@mail.gmail.com> (raw)
In-Reply-To: <4BF25A91-3F02-49A2-A546-A9CF7881E0ED@arm.com>

[-- Attachment #1: Type: text/plain, Size: 1864 bytes --]

The serious need is that we need to patch all the scripts that ask for
python to add a 3 to it. And there will be more of these going forward, not
less. I’d rather just always have python available. Not a problem worth
deliberating over to be honest.

Alex

On Tue 22. Nov 2022 at 18.41, Ross Burton <Ross.Burton@arm.com> wrote:

> On 22 Nov 2022, at 04:42, Markus Volk via lists.openembedded.org <f_l_k=
> t-online.de@lists.openembedded.org> wrote:
> > On Mon, Nov 21 2022 at 06:48:07 PM +0100, Alexander Kanavin <
> alex.kanavin@gmail.com> wrote:
> >> On my Debian systems, indeed, /usr/bin/python is absent.
> >
> > Debian has a package for this
> > https://packages.debian.org/bookworm/python-is-python3
>
> And that’s a perfectly good solution that I like.
>
> Personally, I think people should forget that /usr/bin/python exists: the
> recommendation from Python is to call python2 or python3.  I can quote from
> PEP-0394:
>
> “””
> Depending on a distribution or system configuration, python may or may not
> be installed. If python is installed its target interpreter may refer to
> python2 or python3.”
>
> …
>
>     • Distributors may choose to set the behavior of the python command as
> follows:
>         • python2,
>         • python3,
>         • not provide python command,
>         • allow python to be configurable by an end user or a system
> administrator.
> “””
>
> We’ve picked option 3.  As per Python upstream, that’s absolutely fine.
>
> If you have a serious need that /usr/bin/python exists, and is a symlink
> to python3, then could you not make a simple recipe that RDEPENDS on
> python3 and ships just a /usr/bin/python -> python3 symlink?  You can even
> put this in your layer to avoid having to debate it with the oe-core
> maintainers.
>
> Ross

[-- Attachment #2: Type: text/html, Size: 2620 bytes --]

  reply	other threads:[~2022-11-22 18:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-20 17:52 [oe-core][PATCH] python3: add ${bindir}/python symlink Markus Volk
2022-11-20 18:00 ` Alexander Kanavin
2022-11-20 18:03   ` Markus Volk
2022-11-20 23:17 ` Khem Raj
2022-11-20 23:56   ` Alexander Kanavin
2022-11-21 15:16     ` Khem Raj
2022-11-21 17:18       ` Alexander Kanavin
     [not found]       ` <1729A925BA1D06C8.25787@lists.openembedded.org>
2022-11-21 17:48         ` Alexander Kanavin
2022-11-22  4:42           ` f_l_k
2022-11-22 17:41             ` Ross Burton
2022-11-22 18:03               ` Alexander Kanavin [this message]
2022-11-22 18:14                 ` Richard Purdie
2022-11-22 18:32                   ` Alexander Kanavin
2022-11-22 22:28                     ` Alexandre Belloni
2022-11-23  5:14                       ` Peter Kjellerstedt
2022-11-23 10:06                     ` Ross Burton
2022-11-23  9:59                 ` Ross Burton
2022-11-23 10:55                   ` Alexander Kanavin
2022-11-23 16:34                     ` Khem Raj
2022-11-23 20:02                       ` Ross Burton
2022-11-22 18:13               ` Markus Volk

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=CANNYZj9uxKov0vrox7N3kv-HdQJ9VDbLu7Jsn_SuVUTz_Nbrzw@mail.gmail.com \
    --to=alex.kanavin@gmail.com \
    --cc=Ross.Burton@arm.com \
    --cc=f_l_k@t-online.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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.