From: Balint Reczey <balint.reczey@canonical.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 45655@debbugs.gnu.org
Subject: bug#45655: Please use 'python3' command instead of 'python'
Date: Sun, 10 Jan 2021 18:49:06 +0100 [thread overview]
Message-ID: <CAG+KjmMfB5JYsx8mnJmUMV9=fds0sOokLg-hYEye+gHcyt6SYA@mail.gmail.com> (raw)
In-Reply-To: <jwv5z44bsi7.fsf-monnier+emacs@gnu.org>
Hi Stefan,
On Sun, Jan 10, 2021 at 6:42 PM Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>
> > Python 2 reached EOL about a year ago thus the 'python' command may be
> > missing on some systems.
> > 'python3' is the standard way of invoking the Python 3 interpreter,
> > thus Emacs would have a better chance trying that.
>
> At least here on Debian, `python` redirects to `python3` or `python2`
> depending on some user choice (by installing either `python-is-python3`
> or `python-in-python2`).
>
> So I think it makes a lot of sense to keep using `python` rather than
> `python3`.
I don't think keeping `python` is a good idea, this would make Emacs
considered to be buggy in Debian.
Please see https://wiki.debian.org/Python :
...
NOTE: Debian testing (bullseye) has removed the "python" package and
the '/usr/bin/python' symlink due to the deprecation of Python 2. No
packaged scripts should depend on the existence of '/usr/bin/python':
if they do, that is a bug that should be reported to Debian. You can
use the 'python-is-python3' or 'python-is-python2' packages to restore
an appropriate '/usr/bin/python' symlink for third-party or legacy
scripts.
...
Cheers,
Balint
--
Balint Reczey
Ubuntu & Debian Developer
next prev parent reply other threads:[~2021-01-10 17:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 15:14 bug#45655: Please use 'python3' command instead of 'python' Balint Reczey
2021-01-06 16:59 ` Glenn Morris
2021-01-06 17:47 ` Balint Reczey
2021-01-10 14:49 ` Lars Ingebrigtsen
2021-01-10 17:42 ` Stefan Monnier
2021-01-10 17:49 ` Balint Reczey [this message]
2021-01-10 20:48 ` Stefan Monnier
2021-01-11 5:17 ` Pankaj Jangid
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='CAG+KjmMfB5JYsx8mnJmUMV9=fds0sOokLg-hYEye+gHcyt6SYA@mail.gmail.com' \
--to=balint.reczey@canonical.com \
--cc=45655@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).