From: Markus Volk <f_l_k@t-online.de>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [oe-core][PATCH] python3: add ${bindir}/python symlink
Date: Sun, 20 Nov 2022 19:03:09 +0100 [thread overview]
Message-ID: <9HRNLR.0DY4ZHTXLE82@t-online.de> (raw)
In-Reply-To: <CANNYZj_QqqH5FzZHke2W2yKbP+YHhfHkf4kT7ahtBpkOv2OV9w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 472 bytes --]
Am So, 20. Nov 2022 um 19:00:39 +0100 schrieb Alexander Kanavin
<alex.kanavin@gmail.com>:
> I have to ask you to resend and drop the DISTRO_FEATURE idea. We do
> not want to make the impression that python2 is supported in any way,
> and as explained earlier this implies that all scripts that ask for
> python would work with both 2 and 3. No, this is a clean break, and
> anyone who still has 2.x stuff has to adjust it to ask for
> #!/usr/bin/python2.
I fully agree
[-- Attachment #2: Type: text/html, Size: 636 bytes --]
next prev parent reply other threads:[~2022-11-20 18:03 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 [this message]
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
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=9HRNLR.0DY4ZHTXLE82@t-online.de \
--to=f_l_k@t-online.de \
--cc=alex.kanavin@gmail.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