From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Jani Nikula <jani.nikula@intel.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
linux-kernel@vger.kernel.org, workflows@vger.kernel.org,
Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH v2 3/2] docs: changes: better document Python needs
Date: Tue, 29 Jul 2025 15:44:37 +0200 [thread overview]
Message-ID: <20250729154437.6cbd2788@sal.lan> (raw)
In-Reply-To: <fd1372a9fb57a1372db5b3c0992a929f90183f83@intel.com>
Em Tue, 29 Jul 2025 13:45:26 +0300
Jani Nikula <jani.nikula@intel.com> escreveu:
> On Mon, 28 Jul 2025, Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:
> > Considering the above, for me it seems that the bus already departed:
> > there are several cases where Python is required during build time.
>
> FWIW, if it was up to me, I'd make Python 3+ a non-optional build
> dependency. I'd also forget about any Python 2 backward compat stuff.
I don't think we should do much effort to support Python 2, but it comes
almost for free: only shebang needs to be different, and, if the comments
inside the doc contains non-utf8 chars, an encoding line.
The current tools during Kernel build currently supports it (again,
except for shebang).
Anyway, from my side I'm happy either way.
> I would find it very useful for code/header generation during build
> time, instead of having to resort to C hostprogs. Similar to what MSM is
> doing.
>
> That said, I know there's going to be people vehemently opposed.
Fine from my side ;-) There are some precedents here, so I guess it
should be up to each subsystem to decide using it or not.
> > So, adding a "depends on TOOL_PYTHON" doesn't seem to be trivial.
>
> Agreed. Forget about that idea.
>
>
> BR,
> Jani.
>
>
next prev parent reply other threads:[~2025-07-29 13:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1752307866.git.mchehab+huawei@kernel.org>
2025-07-12 8:32 ` Mauro Carvalho Chehab
2025-07-12 16:31 ` Laurent Pinchart
2025-07-12 22:25 ` Mauro Carvalho Chehab
2025-07-13 9:27 ` Laurent Pinchart
2025-07-24 14:42 ` Jonathan Corbet
2025-07-24 17:43 ` Mauro Carvalho Chehab
2025-07-28 9:28 ` Jani Nikula
2025-07-28 15:33 ` Mauro Carvalho Chehab
2025-07-29 10:45 ` Jani Nikula
2025-07-29 13:44 ` Mauro Carvalho Chehab [this message]
2025-07-29 15:04 ` Jani Nikula
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=20250729154437.6cbd2788@sal.lan \
--to=mchehab+huawei@kernel.org \
--cc=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=jani.nikula@intel.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=workflows@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox