|
From: | kobarity |
Subject: | bug#70815: [PATCH] ; Enahnce python-tests.el to adapt different python interpreters |
Date: | Sun, 26 May 2024 21:05:55 +0900 |
User-agent: | Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM-LB/1.14.9 (Gojō) APEL-LB/10.8 EasyPG/1.0.0 Emacs/30.0.50 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) |
Mattias Engdegård wrote: > This change caused python-tests failures on macOS. See attached log. > > On this machine which has the standard macOS Python installation, 'python' is > python 2, which apparently the tests don't cope very well with. (Have you > verified that they do?) > > The tests pass if modified to prefer Python 3: > > @@ -3722,2 +3722,2 @@ python-tests-get-shell-interpreter > - (cl-some #'executable-find '("python" "python3" "python2")))))) > + (cl-some #'executable-find '("python3" "python" "python2")))))) 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?
[Prev in Thread] | Current Thread | [Next in Thread] |