Thanks for opening the issue. From the pythondotorg issue, the output from the failed command:
Last login: Sat May 8 17:08:01 on ttys005
/Applications/Python\ 3.9/Install\ Certificates.command ; exit;
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LC_ALL = (unset),
LC_CTYPE = "en_AU.UTF-8.UTF-8",
LANG = "en_AU.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
[cnd@mac ~]$ /Applications/Python\ 3.9/Install\ Certificates.command ; exit;
-- pip install --upgrade certifi
/Library/Frameworks/Python.framework/Versions/3.9/bin/python3.9: No module named pip
Traceback (most recent call last):
File "", line 44, in
File "", line 24, in main
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/subprocess.py", line 373, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/Library/Frameworks/Python.framework/Versions/3.9/bin/python3.9', '-E', '-s', '-m', 'pip', 'install', '--upgrade', 'certifi']' returned non-zero exit status 1.
logout
[Process completed]
So the failure is due to pip not being installed. Install Certificates assumes pip will be available but that may not necessarily be the case, for instance, if a custom install of Python was selected and the "Install or upgrade pip" package is deselected. Install Certificates should protect itself, if nothing else, by providing a useful message.
(For the record, the "perl warnings" at the start of the terminal session are presumably coming from one of the shell startup scripts that are run automatically at the beginning of a terminal session. Install Certificates does not use perl.)
|