-
-
Notifications
You must be signed in to change notification settings - Fork 173
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
Pin cryptography to versions compatible with pyopenssl #913
Pin cryptography to versions compatible with pyopenssl #913
Conversation
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
fyi @conda-forge/cryptography |
I should have checked more carefully. I opened a duplicate in #918. Either should work. I certainly won't be offended if you close mine. I do the tightening slightly differently, as detailed in #918 (comment). It would be great to get one of these merged soon, since I suspect this may be causing some fairly widespread breakage. |
I'm not overly opinionated on which approach we take - AFAICT your approach would also fix the issue and does not seem overly constraining. The one thing I would say about your approach is that it could probably be made simpler by removing the existing version constraint, and just converting your
Agreed. Could a member of @conda-forge/core please approve and merge either one? |
@h-vetinari could you please take a look at this PR and PR ( #918 )? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
After sleeping on this, I think that my pins are slightly better because they are monotone. (With this version there is a very slight risk that the solver finds a local optimum with pyopenssl 21.0.0 and cryptography 41 since pyopenssl 22.0.0 requires cryptography <39.) I think the comments here are more informative, so I'm going to copy those to my branch in #918. |
Sorry, I saw #918 first. They are quite similar and thank you both. (I was still investigating this yesterday but this seems to be the right fix.) |
Thanks @ocefpaf! I will open a new PR with proper attribution to ensure that @IzerOnadimQC's informative comments are preserved. |
Checklist
generate_patch_json.py
if absolutely necessary.pre-commit run -a
and ensured all files pass the linting checks.python show_diff.py
and posted the output as part of the PR.Diff output