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

Previous Next

Full log

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

From: Mattias Engdegård <mattias.engdegard <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: kobarity <at> gmail.com, sunlin7.mail <at> gmail.com,
 Stefan Kangas <stefankangas <at> gmail.com>, 70815 <at> debbugs.gnu.org
Subject: Re: bug#70815: [PATCH] ; Enahnce python-tests.el to adapt different
 python interpreters
Date: Mon, 27 May 2024 14:20:21 +0200

27 maj 2024 kl. 13.18 skrev Eli Zaretskii <eliz <at> gnu.org>:

>> If we don't want to do that, it makes more sense to prefer Python 3.
>> This given that Python 2 is EOL since 4+ years, and is less and less
>> likely to be relevant.
> 
> Mattias's message in this thread indicates otherwise, I think.

The `python` binary can very well be the one nobody wants to use, it's just that it has a long-term legacy lease on the file name. For example, on this system (with the unmodified system default Python installations):

|~% python
|
|WARNING: Python 2.7 is not recommended. 
|This version is included in macOS for compatibility with legacy software. 
|Future versions of macOS will not include Python 2.7. 
|Instead, it is recommended that you transition to using 'python3' from within Terminal.

I very much agree that we should make our own decision about what platforms and versions to support but in this case it's just a matter of what we want to use for testing our own code, and given more than one Python, the one named `python3` is more likely to be relevant than just `python`.

Previous Next

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