From: Randy MacLeod <randy.macleod@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: kweihmann@outlook.com, openembedded-core@lists.openembedded.org,
Jiaying.Song.CN@windriver.com
Subject: Re: [OE-core] [scarthgap][master][PATCH] python3: provide /usr/bin/python as a symlink to python3
Date: Tue, 23 Jul 2024 14:41:49 -0400 [thread overview]
Message-ID: <a3be70ca-fe5d-431b-9046-eacaf74212ca@windriver.com> (raw)
In-Reply-To: <CANNYZj9_8v+c_ddG8OOYcBgOidWQdLDMj5pJeTW9uGZk8fBw=w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 493 bytes --]
On 2024-07-23 1:56 p.m., Alexander Kanavin wrote:
> - if anyone is still using python 2.x in target images in 2024 with
> yocto master (nevermind that the public python2 layer is dead and
> unmaintained), and is relying on python 2.x being symlinked to python,
No one that I know if is doing this.
> they should be adjusting their scripts to point to python2 instead.
Yes, this is what I was recommending or at least what I was intending to
recommend.
--
# Randy MacLeod
# Wind River Linux
[-- Attachment #2: Type: text/html, Size: 1031 bytes --]
next prev parent reply other threads:[~2024-07-23 18:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 2:32 [scarthgap][master][PATCH] python3: provide /usr/bin/python as a symlink to python3 jiaying.song.cn
2024-07-18 22:47 ` [OE-core] " Denys Dmytriyenko
2024-07-19 6:17 ` Alexander Kanavin
2024-07-19 6:18 ` Alexander Kanavin
2024-07-19 16:46 ` Denys Dmytriyenko
2024-07-23 13:38 ` Konrad Weihmann
2024-07-23 16:44 ` [OE-core] " Randy MacLeod
2024-07-23 17:56 ` Alexander Kanavin
2024-07-23 18:18 ` Konrad Weihmann
2024-07-23 18:25 ` Alexander Kanavin
2024-07-23 18:41 ` Randy MacLeod [this message]
2024-07-24 16:01 ` Richard Purdie
2024-07-24 16:17 ` Alexander Kanavin
2024-07-24 16:36 ` Martin Jansa
2024-07-24 16:44 ` Alexander Kanavin
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=a3be70ca-fe5d-431b-9046-eacaf74212ca@windriver.com \
--to=randy.macleod@windriver.com \
--cc=Jiaying.Song.CN@windriver.com \
--cc=alex.kanavin@gmail.com \
--cc=kweihmann@outlook.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