GNU bug report logs - #70815
[PATCH] ; Enahnce python-tests.el to adapt different python interpreters

Previous Next

Package: emacs;

Reported by: Lin Sun <sunlin7.mail <at> gmail.com>

Date: Tue, 7 May 2024 06:54:02 UTC

Severity: normal

Tags: patch

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


Message #55 received at 70815 <at> debbugs.gnu.org (full text, mbox):

From: Mattias EngdegÄrd <mattias.engdegard <at> gmail.com>
To: kobarity <kobarity <at> gmail.com>
Cc: Eli Zaretskii <eliz <at> gnu.org>, Lin Sun <sunlin7.mail <at> gmail.com>,
 stefankangas <at> gmail.com, 70815 <at> debbugs.gnu.org
Subject: Re: bug#70815: [PATCH] ; Enahnce python-tests.el to adapt different
 python interpreters
Date: Sun, 26 May 2024 14:21:28 +0200
26 maj 2024 kl. 14.05 skrev kobarity <kobarity <at> gmail.com>:

> All ERTs pass with Python 2 on Linux (Ubuntu 22.04).  So it seems to
> me that this is an issue with Python 2 on Mac.  Maybe the workaround
> using "tty.setraw(0)" is not working with Python 2 on Mac?  Could you
> test if the native completion is working with Python 2?

Not sure how to test that, but if I run python 2 interactively from a terminal then no completion appears to be active (although I'm not sure if something could make it work).

Given the status of Python 2 in general and on macOS in particular (there is a warning that it is only present for compatibility with legacy software) this is not very surprising. I don't think it's something we need to fix in Emacs.

Is there a reason not to apply the suggested patch to prefer `python3` to `python`?
Or put differently, why would `python-shell-interpreter` and `python-tests-get-shell-interpreter` use different preferences?





This bug report was last modified 1 year and 40 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.