Make load_payload()
signature consistent between types
#75
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.
Fixes #74.
The
JSONWebSignatureSerializer.load_payload
signature change is potentially breaking if anybody passedreturn_header
as a second non-keyword argument to the method in the past.itsdangerous.py
itself is using kwargs correctly everywhere so this shouldn't be an issue.For the mixin, the change ensures it will pass additional arguments correctly.