Fix Python ImportError when loading data (itsdangerous serializer) #501
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
Hi maintainers, Just a gentle ping on this PR in case it slipped through the cracks. Happy to make any changes or add tests if needed. Thanks for taking a look! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR fixes an ImportError when loading data with newer versions of
itsdangerous, where TimedJSONWebSignatureSerializer is no longer available.
The code now falls back to URLSafeTimedSerializer, maintaining backward
compatibility with older itsdangerous versions.
Testing:
the TimedJSONWebSignatureSerializer ImportError.
Windows/Python 3.13 environment, which is unrelated to this fix.
Fixes #461