From: Jonathan Corbet <corbet@lwn.net>
To: "Bence Csókás" <bence.csokas@arm.com>, linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Akira Yokosawa <akiyks@gmail.com>,
Jani Nikula <jani.nikula@linux.intel.com>
Subject: Re: [PATCH 0/2] Move Python modules to tools/lib/python
Date: Thu, 27 Nov 2025 10:18:07 -0700 [thread overview]
Message-ID: <875xavwg1c.fsf@trenco.lwn.net> (raw)
In-Reply-To: <61a0b2e5-fa53-4ed2-af26-c519a03a9dc9@arm.com>
Bence Csókás <bence.csokas@arm.com> writes:
> Hi,
>
> On 11/10/25 23:04, Jonathan Corbet wrote:
>> scripts/lib was always a bit of an awkward place for Python libraries; give
>> them a proper home under tools/lib/python. Put the modules from
>> tools/docs/lib there for good measure.
>>
>> The second patch ties them into a single package namespace. It would be
>> more aesthetically pleasing to add a kernel layer, so we could say:
>>
>> from kernel.kdoc import kdoc_parser
>
> This is great, the code looks so much cleaner! However, it would've been
> even nicer if the redundant `kdoc_` was done away with.
>
> So instead of:
> * `import kdoc.kdoc_files` -> `import kdoc.files`
> * `kdoc/kdoc_files.py` -> `kdoc/kdoc_files.py`
> * `abi/abi_parser.py` -> `abi/parser.py`
>
> etc.
>
> Will you consider this?
We can certainly consider it...that's a relatively small detail, though,
in the big organizational picture, so I wasn't concerned about it at
this point.
Thanks,
jon
prev parent reply other threads:[~2025-11-27 17:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 22:04 Jonathan Corbet
2025-11-10 22:04 ` [PATCH 1/2] docs: Move the python libraries " Jonathan Corbet
2025-11-10 22:04 ` [PATCH 2/2] docs: bring some order to our Python module hierarchy Jonathan Corbet
2025-11-18 16:27 ` [PATCH 0/2] Move Python modules to tools/lib/python Jonathan Corbet
2025-11-18 19:16 ` Mauro Carvalho Chehab
2025-11-26 17:59 ` Bence Csókás
2025-11-27 17:18 ` 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=875xavwg1c.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=akiyks@gmail.com \
--cc=bence.csokas@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®