Linux Perf Users
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
	James Clark <james.clark@linaro.org>,
	Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
	linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 1/1] perf: Fix Python 3.6 build breakage in jevents.py and util/setup.py
Date: Fri, 25 Sep 2026 23:52:37 +0200	[thread overview]
Message-ID: <arbtJUe-jizeRugc@x2> (raw)
In-Reply-To: <CAP-5=fW3yv2u4MS1TrbLe4iBL_MyfJx3m4KvP5visKsmT_qwvg@mail.gmail.com>

On Fri, Sep 25, 2026 at 02:29:12PM -0700, Ian Rogers wrote:
> On Fri, Sep 25, 2026 at 2:14 PM Arnaldo Carvalho de Melo
> <acme@kernel.org> wrote:
> >
> > On Fri, Sep 25, 2026 at 01:57:06PM -0700, Ian Rogers wrote:
> > > On Fri, Sep 25, 2026 at 1:47 PM Arnaldo Carvalho de Melo
> > > <acme@kernel.org> wrote:
> > > >
> > > > perf's build still accepts Python 3.6: Makefile.config only rejects
> > > > interpreters older than 3.6 and jevents.py keeps its own removesuffix()
> > > > shim for it, but two recently added constructs are evaluated when the
> > > > module or the function is defined and only work on newer interpreters.
> > >
> > > Could we remove the shim and bump the minimum Python version to 3.9 to
> > > be in line with the rest of the kernel build?
> > > https://github.com/torvalds/linux/blob/master/Documentation/process/changes.rst
> >
> > Since RHEL8 based systems will still be in use for a long time and new
> > perf versions can be useful in solving problems in such systems, maybe
> > we should keep the support on 3.6 as is now :-\
> >
> > This patch is not that big and fixes the only cases where python 3.6 was
> > breaking, so maybe this is not unreasonable to do.
> 
> Could we update the review prompts for this then? Currently the
> prompts load from changes.rst:
> https://github.com/masoncl/review-prompts/blob/main/kernel/subsystem/build.md
> and so Python 3.9. We can then comment that we're doing this for RHEL8 support.

I didn't know about python 3.9 being the minimal version for kernel
python usage.
 
> RHEL8 appears to be in maintenance mode:
> https://endoflife.date/rhel
> which means "New functionality and new hardware enablement are not
> planned for availability in the Maintenance Support Phase."
> https://access.redhat.com/support/policy/updates/errata#Maintenance_Support_Phase
> So is RHEL8 support only necessary for people building the code
> themselves? In that case, they could also update their Python?

Fair enough, I'm reworking the patch to instead make 3.9 be the minimal
for perf as well.

- Arnaldo

  reply	other threads:[~2026-09-25 21:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25 20:47 [PATCH 1/1] perf: Fix Python 3.6 build breakage in jevents.py and util/setup.py Arnaldo Carvalho de Melo
2026-09-25 20:54 ` sashiko-bot
2026-09-25 20:57 ` Ian Rogers
2026-09-25 21:14   ` Arnaldo Carvalho de Melo
2026-09-25 21:29     ` Ian Rogers
2026-09-25 21:52       ` Arnaldo Carvalho de Melo [this message]
2026-09-25 22:20         ` Ian Rogers

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=arbtJUe-jizeRugc@x2 \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=namhyung@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