On Tue, 29 Jul 2025, Akira Yokosawa <akiyks@xxxxxxxxx> wrote: > Hi, > > On Mon, 28 Jul 2025 16:54:28 +0200, Mauro Carvalho Chehab wrote: >> While we do need at least 3.6 for kernel-doc to work, and at least >> 3.7 for it to output functions and structs with parameters at the >> right order, let the python binary be compatible with legacy > code? > >> versions. >> > [...] >> >> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@xxxxxxxxxx> >> --- >> scripts/kernel-doc.py | 37 ++++++++++++++++++++++++++----------- >> 1 file changed, 26 insertions(+), 11 deletions(-) >> >> diff --git a/scripts/kernel-doc.py b/scripts/kernel-doc.py >> index fc3d46ef519f..d4f9188d6a19 100755 >> --- a/scripts/kernel-doc.py >> +++ b/scripts/kernel-doc.py >> @@ -1,9 +1,19 @@ >> -#!/usr/bin/env python3 >> +#!/usr/bin/env python > > This would conflict with my existing setup which has > /usr/bin/python3 only. > > Please don't do this! Agreed, this breaks more than it fixes. Python 2.7 reached end-of-life over five years ago. Do we really have to cater for ancient stuff? Which actual real world cases do not have Python 3+ available? Please just let it go, and see if anyone ever notices? BR, Jani. -- Jani Nikula, Intel
