-
Notifications
You must be signed in to change notification settings - Fork 31
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
Work correctly with pyjwt 2.x #124
Conversation
Test cases are passing now. Ready for review, I think. |
@athornton great, thank-you. 👏 🙏 It looks good. Merging it in. |
@rufuspollock |
@gil-mahalla we'd need to publish it - i think this is related to #119 |
@gil-mahalla if you've got the source checked out, and you've got Docker installed,
|
@athornton if we could give you access to that repo on our docker hub would you up for pushing updates directly there - i imagine it would help your workflow (and that of others)? |
Sure. In the slightly longer term, we need the GitHub Action workflow to push on definition of a new release tag, I think, but in the interim, doing manual pushes of new artifacts would be OK with me. I'll be back at work January 2, 2024, and we can figure it out from there. |
The actual type of
jwt.encode()
changed frombytes
tostr
in 2.x, but somehow the typing hints aren't keeping up, and the whole JWT typing thing is a can of worms (cf jpadilla/pyjwt#602).So I'm being overly defensive about what we actually got back from there, but returning a string up the call stack and modifying the function signature (and its caller).
This is the minimal necessary work to address #122
Maybe if I get some time in the New Year I can work on modernizing giftless and making its test suite more maintainable.