From: Akira Yokosawa <akiyks@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH v2 00/12] Thrash up the parser/output interface
Date: Fri, 11 Jul 2025 13:29:00 +0900 [thread overview]
Message-ID: <92ff26c0-6952-4f7e-965e-2f020adb859b@gmail.com> (raw)
In-Reply-To: <20250710233142.246524-1-corbet@lwn.net>
On Thu, 10 Jul 2025 17:31:30 -0600, Jonathan Corbet wrote:
[...]
> Changes since v1:
> - Coding-style tweaks requested by Mauro
> - Drop the reworking of output-text accumulation for now
> - Add a warning for prehistoric Python versions
Serious review of python code is beyond my background, but I did a test
on this against opensuse/leap:15.6's python3-Sphinx_4_2_0, which comes with
python 3.6.15.
Running "./scripts/kernel-doc.py -none include/linux/rcupdate.h" emits this:
------------------------------------------------------------------------
Traceback (most recent call last):
File "./scripts/kernel-doc.py", line 315, in <module>
main()
File "./scripts/kernel-doc.py", line 286, in main
kfiles.parse(args.files, export_file=args.export_file)
File "/linux/scripts/lib/kdoc/kdoc_files.py", line 222, in parse
self.parse_file(fname)
File "/linux/scripts/lib/kdoc/kdoc_files.py", line 119, in parse_file
doc = KernelDoc(self.config, fname)
File "/linux/scripts/lib/kdoc/kdoc_parser.py", line 247, in __init__
self.emit_message(0,
AttributeError: 'KernelDoc' object has no attribute 'emit_message'
------------------------------------------------------------------------
This error appeared in 12/12. No errors with python3 >=3.9.
I'm not sure but asking compatibility with python <3.9 increases
maintainers/testers' burden. Obsoleting <3.9 all together would
make everyone's life easier, wouldn't it?
Thanks, Akira
next prev parent reply other threads:[~2025-07-11 4:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 23:31 [PATCH v2 00/12] Thrash up the parser/output interface Jonathan Corbet
2025-07-10 23:31 ` [PATCH v2 01/12] docs: kdoc; Add a rudimentary class to represent output items Jonathan Corbet
2025-07-10 23:31 ` [PATCH v2 02/12] docs: kdoc: simplify the output-item passing Jonathan Corbet
2025-07-10 23:31 ` [PATCH v2 03/12] docs: kdoc: drop "sectionlist" Jonathan Corbet
2025-07-11 5:50 ` Mauro Carvalho Chehab
2025-07-10 23:31 ` [PATCH v2 04/12] docs: kdoc: Centralize handling of the item section list Jonathan Corbet
2025-07-11 5:52 ` Mauro Carvalho Chehab
2025-07-10 23:31 ` [PATCH v2 05/12] docs: kdoc: remove the "struct_actual" machinery Jonathan Corbet
2025-07-10 23:31 ` [PATCH v2 06/12] docs: kdoc: use self.entry.parameterlist directly in check_sections() Jonathan Corbet
2025-07-10 23:31 ` [PATCH v2 07/12] docs: kdoc: Coalesce parameter-list handling Jonathan Corbet
2025-07-11 5:54 ` Mauro Carvalho Chehab
2025-07-11 12:45 ` Jonathan Corbet
2025-07-10 23:31 ` [PATCH v2 08/12] docs: kdoc: Regularize the use of the declaration name Jonathan Corbet
2025-07-10 23:31 ` [PATCH v2 09/12] docs: kdoc: straighten up dump_declaration() Jonathan Corbet
2025-07-10 23:31 ` [PATCH v2 10/12] docs: kdoc: directly access the always-there KdocItem fields Jonathan Corbet
2025-07-10 23:31 ` [PATCH v2 11/12] docs: kdoc: clean up check_sections() Jonathan Corbet
2025-07-10 23:31 ` [PATCH v2 12/12] docs: kdoc: emit a warning for ancient versions of Python Jonathan Corbet
2025-07-11 5:49 ` Mauro Carvalho Chehab
2025-07-11 4:29 ` Akira Yokosawa [this message]
2025-07-11 7:29 ` [PATCH v2 00/12] Thrash up the parser/output interface Mauro Carvalho Chehab
2025-07-11 13:17 ` Jonathan Corbet
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=92ff26c0-6952-4f7e-965e-2f020adb859b@gmail.com \
--to=akiyks@gmail.com \
--cc=corbet@lwn.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).