From: sashiko-bot@kernel.org
To: "Arnaldo Carvalho de Melo" <acme@kernel.org>
Cc: 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 20:54:25 +0000 [thread overview]
Message-ID: <20260925205425.84F711F00893@smtp.kernel.org> (raw)
In-Reply-To: <arbd4TJm4s9MVjN-@x2>
> 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.
>
> PEP 585's list[...] became subscriptable in Python 3.9, so the module
> level annotations in jevents.py make Kbuild die at import time:
>
> TypeError: 'type' object is not subscriptable
> make[3]: *** [pmu-events/Build:176: .../test-empty-pmu-events.c] Error 1
>
> as seen on almalinux:8 with its python3.6.8, and the list[str]
> parameters of util/setup.py's functions fail the same way when the
> python binding is built.
>
> [ ... ]
> Fixes: cda907c2c3f99 ("perf jevents: Add python type annotations")
> Fixes: 1fa8d81be1eb ("perf python: Clean up and restructure setup.py")
> Fixes: eaab2eb09dc2 ("perf pmu-events: Parallelize JSON and metric pre-computation in jevents.py")
> Assisted-by: LLM
> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/arbd4TJm4s9MVjN-@x2?part=1
next prev parent reply other threads:[~2026-09-25 20:54 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 [this message]
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
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=20260925205425.84F711F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=acme@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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