`install_certificates.command` uses wrong Python in free threading install

[colesbury]

Bug report

Bug description:

The install_certificates.command script always uses the Python in /Library/Frameworks/Python.framework. It should use the PythonT.framework Python when installing free threading Python on macOS.

cpython/Mac/BuildScript/resources/install_certificates.command

Line 3 in 379ab85

/Library/Frameworks/Python.framework/Versions/@PYVER@/bin/python@PYVER@ << "EOF"

Originally reported by @ngoldbaum

CPython versions tested on:

3.13

Operating systems tested on:

macOS

[ned-deily]

As documented here, the optional PythonT.framework provided by the python.org macOS installers for 3.13+ shares the OpenSSL libraries installed by the Python.framework so there is no need for a separate Install Certificates.command for the free-threading variant.

$ python3.13t
Python 3.13.1 experimental free-threading build (v3.13.1:06714517797, Dec  3 2024, 14:12:37) [Clang 15.0.0 (clang-1500.3.9.4)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import ssl
>>> ssl.get_default_verify_paths()
DefaultVerifyPaths(cafile='/Library/Frameworks/Python.framework/Versions/3.13/etc/openssl/cert.pem', capath=None, openssl_cafile_env='SSL_CERT_FILE', openssl_cafile='/Library/Frameworks/Python.framework/Versions/3.13/etc/openssl/cert.pem', openssl_capath_env='SSL_CERT_DIR', openssl_capath='/Library/Frameworks/Python.framework/Versions/3.13/etc/openssl/certs')

[colesbury]

Thanks for the clarification Ned. I forgot about that.