From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] Convert get_feat to Python
Date: Tue, 11 Nov 2025 17:17:41 +0100 [thread overview]
Message-ID: <cover.1762877066.git.mchehab+huawei@kernel.org> (raw)
Hi Jon,
That's the final series to complete the migration of documentation
build: it converts get_feat from Perl to Python.
With that, no Sphinx in-kernel extensions use fork anymore to call
ancillary scripts: everything is now importing Python methods
directly from the libraries.
As we don't have a definition yet for the location of the Python
libraries yet, I opted to place the parse features library inside
tools/docs/lib. It shouldn't be hard to move it elsewhere once we
define a better place for them.
There's nothing special on this conversion: it is a direct translation,
almost bug-compatible with the original version (*).
(*) I did solve two or three caveats on patch 1.
Most of the complexity of the script relies at the logic to produce
ReST tables. I do have here on my internal scripts a (somewhat) generic
formatter for ReST tables in Python. I was tempted to convert the logic
to use it, but, as this could cause regressions, I opted to not do it
right now, mainly because the matrix table logic is complex. Also,
I'm tempted to modify a little bit the output there, but extra tests
are required to see if PDF output would work with complex tables (I
remember I had a problem with that in the past). So, I'm postponing
such extra cleanup.
Mauro Carvalho Chehab (3):
tools/docs/get_feat.py: convert get_feat.pl to Python
Documentation/sphinx/kernel_feat.py: use class directly
get_feat.pl: remove it, as it got replaced by get_feat.py
Documentation/sphinx/kernel_feat.py | 24 +-
tools/docs/get_feat.pl | 641 ----------------------------
tools/docs/get_feat.py | 225 ++++++++++
/parse_features.py | 494 +++++++++++++++++++++
4 files changed, 732 insertions(+), 652 deletions(-)
delete mode 100755 tools/docs/get_feat.pl
create mode 100755 tools/docs/get_feat.py
create mode 100755 tools/docs/lib/parse_features.py
--
2.51.1
next reply other threads:[~2025-11-11 16:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 16:17 Mauro Carvalho Chehab [this message]
2025-11-11 16:17 ` [PATCH 1/3] tools/docs/get_feat.py: convert get_feat.pl to Python Mauro Carvalho Chehab
2025-11-11 16:17 ` [PATCH 2/3] Documentation/sphinx/kernel_feat.py: use class directly Mauro Carvalho Chehab
2025-11-11 16:17 ` [PATCH 3/3] get_feat.pl: remove it, as it got replaced by get_feat.py Mauro Carvalho Chehab
2025-11-11 17:09 ` [PATCH 0/3] Convert get_feat to Python Jonathan Corbet
2025-11-11 22:12 ` Mauro Carvalho Chehab
2025-11-18 16:44 ` Jonathan Corbet
2025-11-18 19:10 ` 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.1762877066.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 \
/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.