allow more recent pyopenssl #3541
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi @dimbleby, thank you for your contribution! I'll review and test your change soon. |
petyaslavova
approved these changes
Mar 10, 2025
petyaslavova
pushed a commit
to Kakadus/redis-py
that referenced
this pull request
May 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
per #1873 (comment), #3161, #3404 pinning to an exact version of pyopenssl is undesirable, it makes conflicts much more likely in projects that have their own requirement on that library.
pinning to 20.0.1 is especially bizarre: that release was five years ago, and there have been more than a dozen since.
relax the requirement