Added fix that adds support for PyJWT>=2.0.0a1 while keeping support for PyJWT<=1.7.1

[the-papi]

Fixes #325
Fixes #326

[the-papi]

I also think that you should make hotfix release. Many people have trouble with this change.

[Andrew-Chen-Wang]

@the-papi Thanks for the quick fix. I'm not the release maker, but it's been on everyone's mind. Sorry!

[Andrew-Chen-Wang]

@the-papi I'd also appreciate a quick test case. Somewhere in test_backends.py like doing this: https://github.com/SimpleJWT/django-rest-framework-simplejwt/blob/f511e0aeabc24ec792c66f720f4a059ab1c4180c/tests/test_backends.py#L84-L97

I THINK? Need a test case to test both when it's bytes and when it isn't.

[the-papi]

I am not sure how should I test it. I've changed only the implementation and not the API. The encode method still returns str, which is compatible with all tests.

[the-papi]

We would also need different versions of PyJWT if we want to test both branches.

[Andrew-Chen-Wang]

@the-papi Ah my mistake. Just took a gander in the PyJWT repository and it looks like it's just a breaking change, no option to not decode(). I think I can approve of this (only side-effect of just decreasing coverage).

Also we just published a new release! (although unfortunately it didn't pick up this PR).

[the-papi]

Is it possible to include this change in release 4.5.1 asap? Due to this breaking change, we had to freeze a version of PyJWT in my company.

[Andrew-Chen-Wang]

Yes. Not sure why CircleCI freezes up, but I'll email David again to get a quick patch release. I don't have the power to merge if the status checks aren't completely passing.

[Andrew-Chen-Wang]

@the-papi Can you confirm on your own development branch that SimpleJWT works fine if this is merged?

[the-papi]

Yes, everything works as expected.

Maybe someone broke CircleCI configuration. There have been several changes recently.

[the-papi]

I don't understand CircleCI very much, but test workflow no longer contains jobs for django.

3f3228b#diff-78a8a19706dbd2a4425dd72bdab0502ed7a2cef16365ab7030a5a0588927bf47R118

[Andrew-Chen-Wang]

Yes, but it was a simple name change (like how tox would do it). The tests seem to pass in master, so I think all you need to do is rebase your branch with master.

[the-papi]

Looks like it didn't help.

// Sry for the force push. Had some trouble with git.

[Andrew-Chen-Wang]

@the-papi I recommend 1. deleting your fork since you made the changes on master 2. close this PR and create a new PR. Let's see what happens then

[the-papi]

Ok... will try

[brunohenriquy]

Hey guys, when is the 4.5.1 with this fix is coming out?