-
Notifications
You must be signed in to change notification settings - Fork 434
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
Failure to install cryptography wheels for Python 3.6 #1150
Comments
@asavaritayal, I looked into this. Cryptography provides whl for python 34 abi3. Looks like we do something similar to
We can get around 2 by doing |
Nope, this looks like a pip limitation that requires their issue 6070 to be fixed. I just experimented with a few variations and none will choose the cryptography wheel unless you specify I don't have a recommendation right now other than to engage the projects and see what help we can provide. I'll ping both of them. As a workaround, you could do this (tested separately but these commands need checking):
Renaming the cryptography wheel to include the ABI that you're going to download for in the name (dot separators let you specify multiple compatible versions) and using --find-links will avoid trying to download it again, though it will copy the wheel from |
Thanks @zooba for the workaround and pinging the projects. This issue comes up when we try and download wheels from user's Unless, you are aware of a way to figure out which wheel version would satisfy a given python version. So, figuring out that we need |
Nope, no way to figure that out. Which is why I said a temporary workaround is to special case cryptography (and presumably any others that we hear about). |
Blocked on pip getting updated |
@vrdmr Is this still a valid issue? Can you advice what the action item here should be? |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If you are not the original author (asavaritayal) and believe this issue is not stale, please comment with |
Since the Azure SDK takes a dependency on Cryptography which is a native package, publishing a Python Function App fails asking the user to publish using
--build-native-deps
.This shouldn't be the case since Cryptography does provide version 3.6 compatible wheels, see here - pyca/cryptography#4382
/cc @maiqbal11 @elprans
The text was updated successfully, but these errors were encountered: