From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattias.engdegard@gmail.com>
Cc: kobarity@gmail.com, sunlin7.mail@gmail.com,
stefankangas@gmail.com, 70815@debbugs.gnu.org
Subject: bug#70815: [PATCH] ; Enahnce python-tests.el to adapt different python interpreters
Date: Sun, 26 May 2024 18:52:48 +0300 [thread overview]
Message-ID: <86h6ekwoxb.fsf@gnu.org> (raw)
In-Reply-To: <7CF65AE1-B3AC-40C5-AC82-CE575E5E1831@gmail.com> (message from Mattias Engdegård on Sun, 26 May 2024 15:23:46 +0200)
> From: Mattias Engdegård <mattias.engdegard@gmail.com>
> Date: Sun, 26 May 2024 15:23:46 +0200
> Cc: Lin Sun <sunlin7.mail@gmail.com>,
> stefankangas@gmail.com,
> 70815@debbugs.gnu.org,
> Eli Zaretskii <eliz@gnu.org>
>
> Why select Python 2 in the first place? Is it more important to test Python 2 than Python 3 on other platforms?
Why do you have "python" as python2 when you have Python 3.x
installed? The usual practice is to have "python" invoke the
preferred version, which is normally the latest one.
next prev parent reply other threads:[~2024-05-26 15:52 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 6:53 bug#70815: [PATCH] ; Enahnce python-tests.el to adapt different python interpreters Lin Sun
2024-05-11 9:05 ` Eli Zaretskii
2024-05-11 13:37 ` kobarity
2024-05-11 14:27 ` Lin Sun
2024-05-12 2:06 ` kobarity
2024-05-18 22:20 ` Stefan Kangas
2024-05-19 5:54 ` Eli Zaretskii
2024-05-20 0:08 ` Lin Sun
2024-05-20 15:52 ` kobarity
2024-05-20 17:51 ` Lin Sun
2024-05-21 14:04 ` kobarity
2024-05-21 15:34 ` Lin Sun
2024-05-22 14:38 ` kobarity
2024-05-23 13:09 ` Eli Zaretskii
2024-05-26 10:52 ` Mattias Engdegård
2024-05-26 12:05 ` kobarity
2024-05-26 12:21 ` Mattias Engdegård
2024-05-26 12:36 ` kobarity
2024-05-26 13:23 ` Mattias Engdegård
2024-05-26 14:15 ` kobarity
2024-05-26 15:00 ` kobarity
2024-05-26 15:24 ` Mattias Engdegård
2024-05-27 12:33 ` kobarity
2024-05-27 12:45 ` Eli Zaretskii
2024-05-28 12:30 ` Mattias Engdegård
2024-05-28 15:17 ` kobarity
2024-05-28 16:09 ` Mattias Engdegård
2024-05-29 14:56 ` kobarity
2024-05-30 10:09 ` Mattias Engdegård
2024-06-02 13:20 ` kobarity
2024-06-03 14:02 ` Mattias Engdegård
2024-06-03 14:34 ` kobarity
2024-06-03 16:24 ` kobarity
2024-06-04 14:29 ` kobarity
2024-06-05 10:25 ` Mattias Engdegård
2024-06-05 11:52 ` kobarity
2024-06-08 15:34 ` kobarity
2024-06-09 13:58 ` Mattias Engdegård
2024-06-10 14:57 ` kobarity
2024-06-10 15:44 ` Mattias Engdegård
2024-05-26 15:56 ` Eli Zaretskii
2024-05-26 23:06 ` Stefan Kangas
2024-05-27 11:18 ` Eli Zaretskii
2024-05-27 12:20 ` Mattias Engdegård
2024-05-27 12:43 ` Eli Zaretskii
2024-05-26 15:52 ` Eli Zaretskii [this message]
2024-05-27 10:24 ` Mattias Engdegård
2024-05-27 11:19 ` Lin Sun
2024-05-26 15:36 ` 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=86h6ekwoxb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=70815@debbugs.gnu.org \
--cc=kobarity@gmail.com \
--cc=mattias.engdegard@gmail.com \
--cc=stefankangas@gmail.com \
--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).