Supported cryptography version

[decaz]

flask-jwt-extended/setup.py

Line 33 in 6d726be

extras_require={"asymmetric_crypto": ["cryptography>=3.0,<4.0"]},

There is a new version scheme is being used by cryptography: https://cryptography.io/en/latest/api-stability/#versioning.

[vimalloc]

Thanks for making me aware of this. 👍

[decaz]

@vimalloc could you release a new version, please?

[vimalloc]

@decaz done, it should be publishing and available on pypi momentarily 👍

[smarlowucf]

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.