From: Jonathan Corbet <corbet@lwn.net>
To: 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: Tue, 18 Nov 2025 09:27:05 -0700 [thread overview]
Message-ID: <875xb75msm.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20251110220430.726665-1-corbet@lwn.net>
Jonathan Corbet <corbet@lwn.net> writes:
> 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
>
> ...and have the kernel-specific stuff clearly marked, but that means adding
> an empty directory in the hierarchy, which isn't as pleasing.
>
> There are some other "Python library" directories hidden in the kernel
> tree; we may eventually want to encourage them to move as well.
>
> Jonathan Corbet (2):
> docs: Move the python libraries to tools/lib/python
> docs: bring some order to our Python module hierarchy
In the absence of complaints, I have applied these.
Thanks,
jon
next prev parent reply other threads:[~2025-11-18 16:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 22:04 [PATCH 0/2] Move Python modules to tools/lib/python 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 ` Jonathan Corbet [this message]
2025-11-18 19:16 ` [PATCH 0/2] Move Python modules to tools/lib/python Mauro Carvalho Chehab
2025-11-26 17:59 ` Bence Csókás
2025-11-27 17:18 ` 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=875xb75msm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox