-
-
Notifications
You must be signed in to change notification settings - Fork 240
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
Supported cryptography version #452
Comments
Thanks for making me aware of this. 👍 |
@vimalloc could you release a new version, please? |
@decaz done, it should be publishing and available on pypi momentarily 👍 |
Is there a reason (compatibility wise) to lock the version bounds though? If this package works with older versions of cryptography it would be ideal to support that option. Unnecessarily locking requirement bounds makes it difficult to package downstream where a given distribution might have an older version of cryptography. Having the version locked like this conveys that you "need" cryptography>={some_version} for flask-jwt-extended to work but based on the commit history it doesn't seem like this is actually the case. |
flask-jwt-extended/setup.py
Line 33 in 6d726be
There is a new version scheme is being used by cryptography: https://cryptography.io/en/latest/api-stability/#versioning.
The text was updated successfully, but these errors were encountered: