[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250922000624.0a9c2395@foz.lan>
Date: Mon, 22 Sep 2025 00:06:24 +0200
From: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
To: Jonathan Corbet <corbet@....net>
Cc: Randy Dunlap <rdunlap@...radead.org>, Mark Brown <broonie@...nel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>, Linux Kernel Mailing
List <linux-kernel@...r.kernel.org>, "open list:DOCUMENTATION"
<linux-doc@...r.kernel.org>, Mauro Carvalho Chehab <mchehab@...nel.org>
Subject: Re: linux-next: Tree for Sep 19 (make htmldocs problem)
Em Sun, 21 Sep 2025 15:56:37 -0600
Jonathan Corbet <corbet@....net> escreveu:
> Mauro Carvalho Chehab <mchehab+huawei@...nel.org> writes:
>
> >> I have no idea why
> >> they felt the need to employ it for Sphinx, but they did, so we need to
> >> work with that kind of configuration. Meaning, really, I think we have
> >> to just invoke sphinx-build directly rather than trying to control which
> >> version of Python it may ultimately get.
> >
> > True, but if we ignore PYTHON3 env completely, this will break on
> > other setups where sphinx is installed with a different python version
> > (with includes OpenSUSE non-thumbleweed).
>
> How do those setups work prior to your changes? We didn't have to do
> that dance before, right? What makes it necessary now?
We didn't, but in recent past minimal python version was below 3.6.
I added this after a feedback during patch review that it should be
using PYTHON3 env var to better support Leap and other distros with
native python version < 3.7 and would require a pyhton version override
to build docs.
Thanks,
Mauro
Powered by blists - more mailing lists