-
Notifications
You must be signed in to change notification settings - Fork 45
On systems with older SSL, packages that trigger easy_install fail #134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
It's not obvious, but that's actually |
@dstufft yet another example: https://gist.github.com/ilovezfs/ad434ccb5849584f9234f33791486468 Same problem? |
That's running with this diff
(I switched it to Python 3 the other day because I was running into the brownout errors and thought it was conan specific) |
Yes, this is the relevant bit of the output:
You can see pip is executing the |
@dstufft any suggested workarounds for these other than the use-non-Apple-Python sledgehammer? |
You can pre-install whatever is in |
I have macOS "High Sierra" (10.13.3) and we use Python 3.4.4 with a 'venv' for each project; the rather obscure error message "Could not find a version that satisfies the requirement ..." occurs within the first 15 minutes of each hour, due to the TLS 'brownouts' apparently: https://status.python.org/ When the 'pip install' command succeeds, the usual upgrade prompt appears (with a new VE): Upgrading to pip 9.0.3 resolves the 'brownout' issue I believe but I cannot perform the upgrade until after the 15 minute 'closed window' is over! Given that the Mac itself relies on Python 2.7, is there a system-wide way to upgrade pip without having to call upon PyPi? Better, could the Python distribution include the latest version of pip? I really don't see why we should be expected to upgrade pip each time, especially when this 'brownout' policy is in place. |
We recommend that people upgrade their local versions of
I sent out a note recommending this to people on pre-High Sierra versions of macOS; I think this should work for you as well. I defer to others' assessments on this. |
You're using a python release from 2015. If you upgrade to the latest 3.6 release, then it does indeed include the latest version of pip. |
I just filed this against setuptools as suggested. Is there a good workaround other than manually pre-installing the setup_requires packages? |
Either pre-install the packages, or use a Python linked against a newer
OpenSSL. Those are pretty much the only two options ATM.
…On Mon, Apr 9, 2018 at 9:00 PM, Ben Kraft ***@***.***> wrote:
I just filed this against setuptools as suggested. Is there a good
workaround other than manually pre-installing the setup_requires packages?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#134 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAADBPJvPgCgb0XZW-WYHDIJSuVIbXclks5tnAQ6gaJpZM4TCVg_>
.
--
"I disapprove of what you say, but I will defend to the death your right to
say it." -- Evelyn Beatrice Hall (summarizing Voltaire)
"The people's good is the highest law." -- Cicero
GPG Key fingerprint: D1B3 ADC0 E023 8CA6
|
The best recommendation is for the project to declare its build requirements in pyproject.toml per PEP 518, which will satisfy the requirements on a |
but
CC @alex
This is running with
The text was updated successfully, but these errors were encountered: