Update dependency on cryptography (1.7.x) #307
Merged
Conversation
This file contains 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
Changes in 1.7.x depend on behavior introduced in cryptography 2.5
|
The pylint checks are currently failing because GitHub Actions recently added support for Python 3.9, and 3.9 seems to have a bug with pylint: pylint-dev/pylint#3882 |
Python3.9 and pylint currently do not play nicely together
scottarc
approved these changes
Oct 29, 2020
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.
Description of changes:
Changes in 1.7.x depend on behavior introduced in cryptography 2.5, so we need to correctly model our dependency.
Additional testing:
If I set the requirement to
~=2.4.2we see failures due to how cryptography checks byte types. If I set the requirement to~=2.5.0, it passes.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.