Use same Python binary for test as in python mode (bug#70815)

* test/lisp/progmodes/python-tests.el
(python-tests-get-shell-interpreter): Try Python executable names
in the same order as we do for `python-shell-interpreter`,
so that we run the test with the one is most likely to be used.

(cherry picked from commit 9c7de10079bb5f803a1744ae1d56399ad7d42ac5)

diff --git a/test/lisp/progmodes/python-tests.el b/test/lisp/progmodes/python-tests.el
index 2494e80ebc09f63120a10071cb55a35ca78764af..171df86a461650f8f10e35ffc7a619fb06fe654d 100644 (file)
--- a/test/lisp/progmodes/python-tests.el
+++ b/test/lisp/progmodes/python-tests.el
@@ -3729,7 +3729,9 @@ If env string EMACS_PYTHON_INTERPRETER exists, use it as preferred one."
                 (or (executable-find interpreter)
                     (error "Couldn't find EMACS_PYTHON_INTERPRETER(%s) in path"
                            interpreter)))
-              (cl-some #'executable-find '("python" "python3" "python2"))))))
+              ;; Use the same order as for the default value of
+              ;; `python-shell-interpreter'.
+              (cl-some #'executable-find '("python3" "python" "python2"))))))
 
 (ert-deftest python-shell-get-process-name-1 ()
   "Check process name calculation sans `buffer-file-name'."