-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Failed to install cryptography 2.6 on macOS and Linux with Python 3.5/3.6/3.7 #4789
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
Hmmmm, I'm not able to reproduce this,
The issue you're having is that you're not getting the wheel for some reason? |
Try Python 3.7. |
I'm getting the same issue. It fails on Python 3.6 and 3.7 but succeeds on Python 2.7 |
Yup, I can reproduce with python3. What the heck. |
Ok, what's happening is that we use abi3 wheels, so we only built a single wheel for all python3 versions. Except for some reason, our wheels aren't being built as abi3 now. We're investigating. |
We haven't changed https://github.com/pyca/cryptography/blob/master/.jenkins/Jenkinsfile-cryptography-wheel-builder in months, so I'm not sure what changed. If anyone understands this, we'd appreciate the assist. |
BTW installation succeed with Python 3.4, but fails with 3.5/3.6/3.7. |
That makes sense, we use python3.4 as our "base" for the abi3 wheels, so we're ending up with normal python3 wheels, instead of abi3 ones. |
This seems to be a pip bug: pypa/pip#6304 |
Ok, landing #4790 and rebuilding our wheels will resolve this. It'll probably be several hours before this is completed (blame it on timezones) -- I'd suggest pinning your cryptography dependencies until we release 2.6.1 |
2.6.1 fixes this. |
@alex we're not getting the wheel with python 2.7 (tried 15 and 16) on Mac, getting this weird message but the Python requirement should be met:
Any idea what this could be? Could |
@ludokx Your issue likely isn't related to the 2.6 problem we resolved. What do you get when you do We stopped shipping wide unicode wheels on macOS specifically because nobody uses them and maintaining that build infrastructure is non-trivial. |
@reaperhulk you're correct, that seems to be the culprit. I just checked with our folks and we pre-build our python (for reasons :)) and that changed recently. The change will be reverted so that we should be fine then. I'm also finally upgrading to 3.6 which works without any issue. Thanks for looking into it! |
anybody coming to this issue because trying to install twine 3.0.0 in a python 3.8 alpine 3.10 container fails with the exact issue listed above? Dockerfile to reproduce the issue: FROM python:alpine
RUN apk add build-base python3-dev libffi-dev
RUN pip install twine Solution RUN apk add build-base python3-dev libffi-dev libressl-dev |
Uh oh!
There was an error while loading. Please reload this page.
The text was updated successfully, but these errors were encountered: