Skip to content

Bumping cryptography upper bound to X+3 #414

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Oct 1, 2021
Merged

Bumping cryptography upper bound to X+3 #414

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 4 additions & 5 deletions setup.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,14 +75,13 @@
'requests>=2.0.0,<3',
'PyJWT[crypto]>=1.0.0,<3',

'cryptography>=0.6,<4',
'cryptography>=0.6,<38',
# load_pem_private_key() is available since 0.6
# https://github.com/pyca/cryptography/blob/master/CHANGELOG.rst#06---2014-09-29
#
# Not sure what should be used as an upper bound here
# https://github.com/pyca/cryptography/issues/5532
# We will go with "<4" for now, which is also what our another dependency,
# pyjwt, currently use.
# And we will use the cryptography (X+3).0.0 as the upper bound,
# based on their latest deprecation policy
# https://cryptography.io/en/latest/api-stability/#deprecation

"mock;python_version<'3.3'",
]
Expand Down