linux-kernel - Re: [PATCH] kbuild: remove PYTHON variable

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAK7LNAQQ=kqhx6REix7j+ZndABjuCBEwp=yiQp71Z0fBrQZxog@mail.gmail.com>
Date:   Tue, 2 Feb 2021 05:58:51 +0900
From:   Masahiro Yamada <masahiroy@...nel.org>
To:     Jonathan Corbet <corbet@....net>
Cc:     Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
        "open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
        Fenghua Yu <fenghua.yu@...el.com>,
        Michal Marek <michal.lkml@...kovi.net>,
        Tony Luck <tony.luck@...el.com>, linux-ia64@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] kbuild: remove PYTHON variable

On Tue, Feb 2, 2021 at 1:38 AM Jonathan Corbet <corbet@....net> wrote:
>
> Masahiro Yamada <masahiroy@...nel.org> writes:
>
> > Python retired in 2020, and some distributions do not provide the
> > 'python' command any more.
> >
> > As in commit 51839e29cb59 ("scripts: switch explicitly to Python 3"),
> > we need to use more specific 'python3' to invoke scripts even if they
> > are written in a way compatible with both Python 2 and 3.
> >
> > This commit removes the variable 'PYTHON', and switches the existing
> > users to 'PYTHON3'.
> >
> > BTW, PEP 394 (https://www.python.org/dev/peps/pep-0394/) is a helpful
> > material.
> >
> > Signed-off-by: Masahiro Yamada <masahiroy@...nel.org>
>
> So this will have the effect of making the docs build impossible for
> folks who only have Python 2.


Is this a problem?  Python 2 is EOL.

Everybody who wants to use Python
must install Python 3.


Rather, people are screaming
that the 'python' command does not exist.




>  As I said before, this is a step that we
> knew was coming, we just hadn't decided on the exact timing - I guess
> this decides for us :)
>
> That said, I'll copy linux-doc to see if anybody screams.  I assume this
> is a 5.12 change?


No, I am planning to do this for 5.11
(a pull request this week if there is no objection).








> Thanks,
>
> jon
>


-- 
Best Regards
Masahiro Yamada