Fix: Support PyJWT 2 and up #27
Merged
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.
The current requirements specify a dependency of
pyjwt < 2. This restriction can cause conflicts in projects using PyJWT 2.x either explicitly or as a dependency of another library.In Python 3 with PyJWT 2.0.1, the token returned is a string type and not bytes, so the
.decode('utf-8')was replaced withsix.enforce_textto support both strings and bytes.There is a typo in one of the tests – jwt.decode expects the kwarg
alogrithms, notalgorithm. This silently passes in PyJWT < 2, but is a requirement in later versions.Finally, I unpinned the dev requirement versions as the specified version of pylint errors in the
3.6environment.🚀