From: Jonathan Corbet <corbet@lwn.net>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Fenghua Yu <fenghua.yu@intel.com>,
Michal Marek <michal.lkml@markovi.net>,
Tony Luck <tony.luck@intel.com>,
linux-ia64@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kbuild: remove PYTHON variable
Date: Mon, 01 Feb 2021 21:21:48 +0000 [thread overview]
Message-ID: <87czxjv5zn.fsf@meer.lwn.net> (raw)
In-Reply-To: <CAK7LNAQQ=kqhx6REix7j+ZndABjuCBEwp=yiQp71Z0fBrQZxog@mail.gmail.com>
Masahiro Yamada <masahiroy@kernel.org> writes:
> On Tue, Feb 2, 2021 at 1:38 AM Jonathan Corbet <corbet@lwn.net> wrote:
>> So this will have the effect of making the docs build impossible for
>> folks who only have Python 2.
>
> Is this a problem? Python 2 is EOL.
>
> Everybody who wants to use Python
> must install Python 3.
I honestly don't know, but people do keep things around for a
surprisingly long time.
>> As I said before, this is a step that we
>> knew was coming, we just hadn't decided on the exact timing - I guess
>> this decides for us :)
>>
>> That said, I'll copy linux-doc to see if anybody screams. I assume this
>> is a 5.12 change?
>
> No, I am planning to do this for 5.11
> (a pull request this week if there is no objection).
I'm not going to truly object and try to block this, but I worry that
it's soon and without warning. It's not a change I would merge for
-rc7. IMO this should be done in 5.12 with an appropriate note added to
Documentation/process/changes.rst as well.
Thanks,
jon
prev parent reply other threads:[~2021-02-01 21:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 1:00 [PATCH] kbuild: remove PYTHON variable Masahiro Yamada
2021-02-01 16:38 ` Jonathan Corbet
2021-02-01 20:58 ` Masahiro Yamada
2021-02-01 21:21 ` Jonathan Corbet [this message]
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=87czxjv5zn.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=fenghua.yu@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=tony.luck@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox