Ned Deily added the comment:
> What exactly is the backport status for this issue, and is there anything
> with more info for this user?
Python 3.6 has been in the security-fix-only phase of its life cycle since
2018-12 which means that python.org binary installers for Mac or Windows
platfo
Steve Arnold added the comment:
I can't seem to find a usable answer for a user on Sierra with a (supposedly)
working python 3.6 install. From what I can tell all the related bugs are
closed except this one, and this one doesn't include python 3.6. Running the
install_certificates.command
Ned Deily added the comment:
So as not to delay 3.8.0b4, I'm removing this as a "release blocker'. Once the
implementation is in master, we can consider backporting to other releases.
--
priority: release blocker -> critical
versions: +Python 3.9
_
Łukasz Langa added the comment:
This is marked as a release blocker. The last 3.8 beta is scheduled for Monday.
Please decide how to proceed ASAP.
--
nosy: +benjamin.peterson, lukasz.langa
priority: deferred blocker -> release blocker
___
Python tra
Raymond Hettinger added the comment:
> I am going to reopen this one and use it to implement a solution
> that eliminates the need to manually run Install Certificates
> at installation time.
There will be much rejoicing. Almost every week, I have a learner bump into
this issue.
--
Ned Deily added the comment:
I do not disagree that the current manual Install Certificates step is not
ideal but, again, for the reasons cited in my earlier response (and other
reasons), adding a dependency on pip to provide certificates is not a good
idea. But, since there does not seem t
Dmitrii Pasechnik added the comment:
The script install_certificates.command depends upon pip, it calls pip to
install certifi. Thus it's no less "optional" than pip.
And pip is only functional, and it able to do the installation in question,
due to it including the certificate in question.
Ned Deily added the comment:
Thanks for the suggestion but that is not a workable solution for two reasons.
One, pip is an optional install with the python.org installer so we cannot
depend on it being available. More importantly, from a packaging point of
view, the internal composition of
New submission from Dmitrii Pasechnik :
Currently (e.g. on the released Python 2.7.16)
Mac/BuildScript/resources/install_certificates.command does install certifi
module from the net and symlinks its cacert.pem to provide openssl with a
working certificate. The same task may be accomplished m
