unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lin Sun <sunlin7.mail@gmail.com>
Cc: 70722@debbugs.gnu.org
Subject: bug#70722: [PATCH] ; Migrate to python3 for (package-test-update-archives-async)
Date: Thu, 02 May 2024 21:54:57 +0300	[thread overview]
Message-ID: <86sez0jb7i.fsf@gnu.org> (raw)
In-Reply-To: <CABCREdpF1c5AK5mZqvdEhvVHK4XVCDqjcRJ8VHxj_Qrhw-u+AQ@mail.gmail.com> (message from Lin Sun on Thu, 2 May 2024 18:11:04 +0000)

> From: Lin Sun <sunlin7.mail@gmail.com>
> Date: Thu, 2 May 2024 18:11:04 +0000
> 
> The test case "package-test-update-archives-async" still tries to
> search "python2" for testing, while python2 was at the end of its life
> years ago.
> So move the test case from python2 to python3.

I'd prefer to make the test support both Python 2.x and Python 3.x.
The fact that python.org end-of-life'd Python 2 doesn't mean we have
to jump to attention and follow suit.  Old systems might still have
Python 2 installed, and there's no need to drop them.

I do agree that we should try looking for Python 3 first, and only
afterwards for Python 2.

Also, I think the test should start by looking for just "python",
before the versioned variants.

E.g., on my system (executable-find "python3") returns nil, although I
have Python 3.x installed -- but it's installed under the name
"python".

Thanks.





  reply	other threads:[~2024-05-02 18:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-02 18:11 bug#70722: [PATCH] ; Migrate to python3 for (package-test-update-archives-async) Lin Sun
2024-05-02 18:54 ` Eli Zaretskii [this message]
2024-05-06  0:28   ` Lin Sun
2024-05-09  8:33     ` Eli Zaretskii
2024-05-09 16:00       ` kobarity
2024-05-09 16:19         ` Lin Sun
2024-05-11 10:07         ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86sez0jb7i.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=70722@debbugs.gnu.org \
    --cc=sunlin7.mail@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).