public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Andi Kleen <ak@linux.intel.com>,
	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: Mon, 30 Sep 2024 14:26:47 -0700	[thread overview]
Message-ID: <ZvsXl2g6kYDi6F9o@google.com> (raw)
In-Reply-To: <CAP-5=fWS-xOPurApZpMA=Zzukt5PQDYjF_7otCPTAL33PYmXAQ@mail.gmail.com>

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
I think it's reasonable to consider removing Python 2 support now.

> 
> The reason is that since moving to linking libraries rather than
> building code we now have the ability to call functions like
> parse_events - previously parse_events was stubbed out because there
> was no way to build lex/yacc code. Calling parse_events is more
> sensible than existing logic that does things like open a legacy
> cycles event only on 1 PMU type. That is, the existing code doesn't
> support hybrid. Practically there is no way to test python2 support
> builds and works without having python2. We shouldn't be in the
> business of installing python2 in 2024, my organization has removed
> all support for over 3 years.

I think the problem nowdays is the container images for old distro.  I'm
not sure how long we need to support them but it should be cut out at
some point.

Thanks,
Namhyung


[1] https://www.python.org/doc/sunset-python-2/

  reply	other threads:[~2024-09-30 21:26 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 [this message]
2024-10-01 11:22         ` Andi Kleen
2024-10-01 12:49           ` James Clark
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=ZvsXl2g6kYDi6F9o@google.com \
    --to=namhyung@kernel.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=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