linux-kernel - Re: [PATCH 0/2] Move Python modules to tools/lib/python

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <875xavwg1c.fsf@trenco.lwn.net>
Date: Thu, 27 Nov 2025 10:18:07 -0700
From: Jonathan Corbet <corbet@....net>
To: Bence Csókás <bence.csokas@....com>,
 linux-doc@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, Mauro Carvalho Chehab
 <mchehab+huawei@...nel.org>, Akira Yokosawa <akiyks@...il.com>, Jani
 Nikula <jani.nikula@...ux.intel.com>
Subject: Re: [PATCH 0/2] Move Python modules to tools/lib/python

Bence Csókás <bence.csokas@....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