From: Jonathan Corbet <corbet@lwn.net>
To: Jani Nikula <jani.nikula@linux.intel.com>,
Akira Yokosawa <akiyks@gmail.com>,
mchehab+huawei@kernel.org
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH 1/2] docs: kernel-doc: avoid script crash on ancient Python
Date: Tue, 29 Jul 2025 07:57:46 -0600 [thread overview]
Message-ID: <877bzrxfol.fsf@trenco.lwn.net> (raw)
In-Reply-To: <e9cf21e5332616f2fb58a90fe8ba6f91359915b8@intel.com>
Jani Nikula <jani.nikula@linux.intel.com> writes:
> Agreed, this breaks more than it fixes.
>
> Python 2.7 reached end-of-life over five years ago. Do we really have to
> cater for ancient stuff? Which actual real world cases do not have
> Python 3+ available? Please just let it go, and see if anyone ever
> notices?
I kind of have to agree. The only real Python 2 user I know about is
OpenOffice.org, which promises to get off any year now. Meanwhile, as I
recall, the advice from the Python project is to say "python3" and not
count on bare "python" being available.
jon
next prev parent reply other threads:[~2025-07-29 13:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 14:54 [PATCH 0/2] Better handle and document Python needs for Kernel build Mauro Carvalho Chehab
2025-07-28 14:54 ` [PATCH 1/2] docs: kernel-doc: avoid script crash on ancient Python Mauro Carvalho Chehab
2025-07-29 10:08 ` Akira Yokosawa
2025-07-29 13:19 ` Jani Nikula
2025-07-29 13:57 ` Jonathan Corbet [this message]
2025-07-28 14:54 ` [PATCH 2/2] docs: changes: better document Python needs Mauro Carvalho Chehab
2025-07-29 10:35 ` Akira Yokosawa
2025-07-29 13:37 ` Mauro Carvalho Chehab
-- strict thread matches above, loose matches on Subject: below --
2025-07-29 6:48 [PATCH 1/2] docs: kernel-doc: avoid script crash on ancient Python kernel test robot
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=877bzrxfol.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=akiyks@gmail.com \
--cc=jani.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.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 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.