From: James Clark <james.clark@linaro.org>
To: Andi Kleen <ak@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>
Cc: 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>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
Xu Yang <xu.yang_2@nxp.com>, Zixian Cai <fzczx123@gmail.com>,
Paran Lee <p4ranlee@gmail.com>, Ben Gainey <ben.gainey@arm.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] perf python: Remove python 2 scripting support
Date: Tue, 1 Oct 2024 13:49:57 +0100 [thread overview]
Message-ID: <d0b29526-1a4a-4bb3-9cfd-9097f8ba7ef7@linaro.org> (raw)
In-Reply-To: <ZvvbiY1NjTZxWvG7@tassilo>
On 01/10/2024 12:22 pm, Andi Kleen wrote:
> On Mon, Sep 30, 2024 at 02:26:47PM -0700, Namhyung Kim wrote:
>> On Thu, Sep 19, 2024 at 06:45:23AM +0200, Ian Rogers wrote:
>>> On Thu, Sep 19, 2024 at 3:29 AM Andi Kleen <ak@linux.intel.com> wrote:
>>>>
>>>> On Thu, Sep 19, 2024 at 12:54:17AM +0200, Ian Rogers wrote:
>>>>> Python2 was deprecated 4 years ago, remove support and workarounds.
>>>>
>>>> Nacked-by: Andi Kleen
>>>>
>>>> I don't see any advantages of breaking perfectly fine existing setups
>>>> for no benefits.
>>
>> Well, I think the benefit is in the maintenance. The EOL of Python 2
>> was 2020/1/1 [1] and we are targeting this release (v6.13) in 2025. So
>
> AFAIK it's still widely used, and supported by third parties. And even
> if not it's not that the python usage in perf needs any external support.
>
> In Linux deprecation is generally tied to nobody using something
> anymore, and that is clearly not the case here.
>
>> I think it's reasonable to consider removing Python 2 support now.
>
> That's code that practically never changes, so I don't see any
> maintenance benefit. I mean it needs to be compile tested / perf tested,
> but Arnaldo's container collection will do that practically
> for free.
>
> -Andi
>
630af16 was quite painful to do and was related to supporting both
python versions, so there is some ongoing cost. If we do this removal we
could remove that one too. Plus Arnaldo could drop the python2
containers and get a faster iteration time.
I think I'm neutral to in favor of removing python2 support. People on
ancient systems would more likely be using an old branch anyway.
James
next prev parent reply other threads:[~2024-10-01 12:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 22:54 [PATCH v1 0/2] Python module cleanup Ian Rogers
2024-09-18 22:54 ` [PATCH v1 1/2] perf python: Remove python 2 scripting support Ian Rogers
2024-09-19 1:29 ` Andi Kleen
2024-09-19 4:45 ` Ian Rogers
2024-09-30 21:26 ` Namhyung Kim
2024-10-01 11:22 ` Andi Kleen
2024-10-01 12:49 ` James Clark [this message]
2024-10-01 13:47 ` Ian Rogers
2024-10-10 1:26 ` Namhyung Kim
2024-10-01 12:52 ` James Clark
2024-09-18 22:54 ` [PATCH v1 2/2] perf python: Constify variables and parameters Ian Rogers
2024-10-01 12:52 ` James Clark
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=d0b29526-1a4a-4bb3-9cfd-9097f8ba7ef7@linaro.org \
--to=james.clark@linaro.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ben.gainey@arm.com \
--cc=fzczx123@gmail.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--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=p4ranlee@gmail.com \
--cc=peterz@infradead.org \
--cc=xu.yang_2@nxp.com \
/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
all inboxes | Powered by JetHome®