unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, Augusto Stoffel <arstoffel@gmail.com>,
	kobarity <kobarity@gmail.com>
Subject: Re: master 7f0a252f216 1/2: Prefer python3 for python-interpreter
Date: Sun, 29 Sep 2024 14:41:15 -0700	[thread overview]
Message-ID: <CADwFkmkaDQX1G-_xT1oOiO2e2Yzz82dBd27zxN_jZbHa51v5DA@mail.gmail.com> (raw)
In-Reply-To: <865xqe4drv.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

> Yes, they will: we now force them to use Python 3.x, even if they
> point the 'python' symlink to Python 2.x.

To the extent that we "force" anyone with user option defaults, we have
already done that with `python-shell-interpreter'.

> What happens when there's Python 4.x? will we change the value again?

Guido has stated publicly that the Python core team intends to basically
just continue incrementing the minor version until the end of time, and
that there will never be a Python 4.  So, luckily for us, it's not
likely to be an issue for a very long time.

> I'm not saying we should necessarily go back to a single fixed value.
> But we could, for example, test "python" before "python3".  That
> should solve the above case.

OK, then let's do that.  It also seems to be Augusto's preferred option.
It should work on all my machines: let's hope that it works without any
problems elsewhere too.

Assuming that we care about consistency between `python-interpreter' and
`python-shell-interpreter' (I think we should), this means reversing the
decision to prefer Python 3 that was made in Emacs 28.1 (commit
fa686f099800).

So I've now made this change in dd4c67907eb.



  reply	other threads:[~2024-09-29 21:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-27  7:12 master 7f0a252f216 1/2: Prefer python3 for python-interpreter Eli Zaretskii
2024-09-27  7:59 ` Xiyue Deng
2024-09-27 18:43   ` Augusto Stoffel
2024-09-27 22:13     ` Xiyue Deng
2024-09-29 15:37     ` Stefan Kangas
2024-09-29 15:49       ` Eli Zaretskii
2024-09-29 16:38         ` Augusto Stoffel
2024-09-29 15:23 ` Stefan Kangas
2024-09-29 15:31   ` Eli Zaretskii
2024-09-29 15:36     ` Eli Zaretskii
2024-09-29 16:05     ` Stefan Kangas
2024-09-29 16:37       ` Eli Zaretskii
2024-09-29 21:41         ` Stefan Kangas [this message]
2024-09-30 11:22           ` Eli Zaretskii
2024-10-05 22:50   ` Rudolf Adamkovič
2024-10-07  8:20     ` Robert Pluim

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=CADwFkmkaDQX1G-_xT1oOiO2e2Yzz82dBd27zxN_jZbHa51v5DA@mail.gmail.com \
    --to=stefankangas@gmail.com \
    --cc=arstoffel@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=kobarity@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).