From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
workflows@vger.kernel.org
Subject: [PATCH 0/2] Better handle and document Python needs for Kernel build
Date: Mon, 28 Jul 2025 16:54:27 +0200 [thread overview]
Message-ID: <cover.1753713955.git.mchehab+huawei@kernel.org> (raw)
Hi Jon,
As promised, I'm sending you the missing patches from the
python backward-compatibility series. They're not urgent,
IMO it should be OK to have them merged for 6.17.
The first patch fix process/changes.rst. Currently, it makes one
think that Python is optional. While not having python may work
on some environments, there are some python scripts called
during Kernel build time that require python.
Document them.
Also, in order to avoid breaking compilation, make kernel-doc's
main script executable with elder Python versions.
Backward-compatibility tested with Python 2.7 and 3.4 (although
it may work since 3.2). On elder versions, it would emit a
warning and do nothing, as the actual code depends on features
at 3.6 (f-strings) and 3.7 (ordered dict).
Mauro Carvalho Chehab (2):
docs: kernel-doc: avoid script crash on ancient Python
docs: changes: better document Python needs
Documentation/process/changes.rst | 13 ++++++++++-
scripts/kernel-doc.py | 37 ++++++++++++++++++++++---------
2 files changed, 38 insertions(+), 12 deletions(-)
--
2.49.0
next reply other threads:[~2025-07-28 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 14:54 Mauro Carvalho Chehab [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
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=cover.1753713955.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=workflows@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox