From: Leo Yan <leo.yan@arm.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] perf build: Add Debian/Ubuntu python-is-python3
Date: Mon, 20 Oct 2025 12:05:40 +0100 [thread overview]
Message-ID: <20251020110540.GF281971@e132581.arm.com> (raw)
In-Reply-To: <CAMuHMdXEBX2CK8iE-Mc0dPR5gV5dBM6QU9LsEWnWgO-d=o6xVg@mail.gmail.com>
Hi Geert,
On Mon, Oct 20, 2025 at 12:15:22PM +0200, Geert Uytterhoeven wrote:
[...]
> > Can we explicitly suggest that developers install python3-devel or
> > python3-dev instead? Two reasons:
> >
> > - python-dev-is-python3 is specific to Ubuntu/Debian; some distros do
> > not provide this package and even advocate against using unversioned
> > "/usr/bin/python" shebangs [1].
> >
> > - As Namhyung mentioned, perf has removed Python 2 support (at least
> > this is claimed), it is straightforward to install only the Python3
> > packages.
>
> Suggesting python3-dev sounds good to me.
It is good to mention both python3-devel / python3-dev (one is for Fedora
and another is for Debian/Ubuntu). Sorry for confusion.
> None of the two checks:
>
> ifndef PYTHON
> $(call disable-python,No python interpreter was found: disables
> Python support - please install python-devel/python-dev)
>
> ifndef PYTHON
> $(error ERROR: No python interpreter found for jevents
> generation. Install python or build with NO_JEVENTS=1.)
>
> seem to be about the python interpreter anyway, but about the python
> development environment.
Either is fine for me.
Thanks,
Leo
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
prev parent reply other threads:[~2025-10-20 11:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 12:44 [PATCH 0/2] perf build: Ubuntu LTS fixes Geert Uytterhoeven
2025-10-16 12:44 ` [PATCH 1/2] perf build: Fix confusing "No python interpreter needed" message Geert Uytterhoeven
2025-10-16 12:44 ` [PATCH 2/2] perf build: Add Debian/Ubuntu python-is-python3 Geert Uytterhoeven
2025-10-17 12:29 ` Leo Yan
2025-10-17 16:39 ` Geert Uytterhoeven
2025-10-19 2:49 ` Namhyung Kim
2025-10-20 9:31 ` Leo Yan
2025-10-20 10:15 ` Geert Uytterhoeven
2025-10-20 11:05 ` Leo Yan [this message]
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=20251020110540.GF281971@e132581.arm.com \
--to=leo.yan@arm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=geert@linux-m68k.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).