From: Ross Burton <Ross.Burton@arm.com>
To: "raj.khem@gmail.com" <raj.khem@gmail.com>
Cc: Alexander Kanavin <alex.kanavin@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: Wed, 23 Nov 2022 20:02:17 +0000 [thread overview]
Message-ID: <A64E29A1-4A6F-4DE1-A102-0121B2097377@arm.com> (raw)
In-Reply-To: <CAMKF1sr7ZxbQPkAydEq6psBZSS=oumi0yogEWXLt23+YyhobCA@mail.gmail.com>
> On 23 Nov 2022, at 16:34, Khem Raj via lists.openembedded.org <raj.khem=gmail.com@lists.openembedded.org> wrote:
>
> If
>> /usr/bin/python is available by default, as it is already on Fedora,
>
> There perhaps is a reason for that in Fedora, but it is in conflict
> with what PEP0384 is saying
It’s not in conflict: the PEP codifies that /usr/bin/python can be python3. Or python2. Or not there at all. Basically, it’s up to the distribution, so people *writing Python* shouldn’t have any assumptions about it.
Ross
next prev parent reply other threads:[~2022-11-23 20:02 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
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 [this message]
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=A64E29A1-4A6F-4DE1-A102-0121B2097377@arm.com \
--to=ross.burton@arm.com \
--cc=alex.kanavin@gmail.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.