All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org,  Justin Tobler <jtobler@gmail.com>
Subject: Re: [PATCH] ci: fix Python dependency on Ubuntu 24.04
Date: Mon, 06 May 2024 10:49:55 -0700	[thread overview]
Message-ID: <xmqq7cg6zv7g.fsf@gitster.g> (raw)
In-Reply-To: <ZjjU_Gaum8iYLks8@tanuki> (Patrick Steinhardt's message of "Mon, 6 May 2024 15:02:52 +0200")

Patrick Steinhardt <ps@pks.im> writes:

> So ultimately, it does not matter which jobs use what. But what does
> matter is whether the image even supports Python 2. And as we nowadays
> do have a fair split of jobs using "ubuntu:20.04" and "ubuntu:latest",
> I'd just use that the the criterium to pick the Python version.
>
> Once we drop support for Ubuntu 20.04, we can then more forward and stop
> supporting Python 2 altogether. Or maybe even earlier than that -- I do
> not think it is reasonable to ask Git to maintain compatibility with a
> project that is end of life already.

Yup.  If an distro sticks to Python 2 for whatever reason, they may
want to donate and dedicate CI resources, but otherwise it is not
really our job to keep compatibility on our side.

>> With this change, "linux-gcc" jobs using ubuntu 20.04 will now use
>> Python 2. Is that what we want?
>
> Well, as explained above, the selection was arbitrary in the first
> place. Now it's less so as the choice is mandated by what is actually
> supported.

Yup, as long as there is one that supports Python 2 among the
distros we happen to use for our CIs, we can pick that one.
Otherwise we should drop.

Dropping Python 2 support does not have to wait for Git 3.0, I would
say.

Thanks.

  reply	other threads:[~2024-05-06 17:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06  5:35 [PATCH] ci: fix Python dependency on Ubuntu 24.04 Patrick Steinhardt
2024-05-06 12:55 ` Justin Tobler
2024-05-06 13:02   ` Patrick Steinhardt
2024-05-06 17:49     ` Junio C Hamano [this message]
2024-05-06 19:06 ` Justin Tobler
2024-05-06 19:28   ` Junio C Hamano
2024-05-07  4:08   ` Patrick Steinhardt

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=xmqq7cg6zv7g.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jtobler@gmail.com \
    --cc=ps@pks.im \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.