From: Augusto Stoffel <arstoffel@gmail.com>
To: "Martín Fernández" <tinchofernandez97@gmail.com>,
"Glenn Morris" <rgm@gnu.org>
Cc: Philip Kaludercic <philipk@posteo.net>, emacs-devel@gnu.org
Subject: Re: python-mode: Why python-interpreter defaults to "python" instead of looking for python/python3
Date: Thu, 16 Mar 2023 19:13:06 +0100 [thread overview]
Message-ID: <87a60cbm4t.fsf@gmail.com> (raw)
In-Reply-To: <CAOVCL7WpmRaY5KR_h1CKDEve=Ti7oZF4XjTEJYkkjei0U50PkQ@mail.gmail.com> ("Martín Fernández"'s message of "Thu, 16 Mar 2023 11:29:28 -0300")
On Thu, 16 Mar 2023 at 11:29, Martín Fernández wrote:
> What do you think? Do you know what the history is for the logic on
> the interpreter variable and why it wasn't implemented on the cmdline
> variable?
I've included Glen, who implemented the logic in bug#45655. I now see
that in that ticket Stefan made exactly the same points I made here.
Namely:
>>>> IMO the logic to choose `python-shell-interpreter' is misguided. The
>>>> default value should be just "python", since if you are doing anything
>>>> with Python and "python" doesn't point to the right version, then you
>>>> are in trouble anyway. OTOH, if you really need to work with Python 2
>>>> and symlink "python" accordingly then the current default proactively
>>>> puts you in trouble.
>>>>
>>>> Personally I'd be happy to see a patch fixing
>>>> `python-shell-interpreter'.
next prev parent reply other threads:[~2023-03-16 18:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 14:03 python-mode: Why python-interpreter defaults to "python" instead of looking for python/python3 Martín Fernández
2023-03-08 19:41 ` Augusto Stoffel
2023-03-16 10:09 ` Augusto Stoffel
2023-03-16 10:18 ` Philip Kaludercic
2023-03-16 14:29 ` Martín Fernández
2023-03-16 18:13 ` Augusto Stoffel [this message]
2023-03-16 18:17 ` Augusto Stoffel
2023-03-16 18:45 ` Yuri Khan
2023-03-17 19:32 ` chad
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=87a60cbm4t.fsf@gmail.com \
--to=arstoffel@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
--cc=rgm@gnu.org \
--cc=tinchofernandez97@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).