Status

[jpadilla]

Hello there,

For a long time now I've honestly thought I'd have the time and energy to come back and work on this project, and I think I still don't. I've not worked on any project recently needing it, which makes it harder to find time to come back.

At some point I also noticed I no longer liked how the project had evolved and that it deserved a fair redesign and there are a few fundamental changes required. Now I'm certain that I wouldn't be able to work on this with the care required for a major version bump.

I'm definitely not proud at how long it has taken me to make this or any update, I recognize that and I'm sorry for not having spoken out sooner.

There's two efforts/projects that I'd like to point out to:

Fork: https://github.com/Styria-Digital/django-rest-framework-jwt
Drop-in updated replacement fork. I'm willing to transfer repo, pypi, etc, to keep this going.

Alternative: https://github.com/davesque/django-rest-framework-simplejwt
Many of the changes that I've wanted to work on are already done here. This is what I would probably use today.

Learned quite a few things from this. Thanks to everyone, including past collaborators and contributors. ❤️

Update:

I've transferred the repository from @getblimp. Neither @getblimp nor @gcollazo are involved with this project anymore.

[jheld]

Can you elaborate on the probable maintenance changeset involved for devs switching to the simple project?

[jpadilla]

@jheld Not entirely sure, but that project has good documentation and slightly based on this one, so I bet it shouldn't be to hard to migrate to it.

[jberends]

I would recommend, to mention in the top of the readme (and thus also op PyPI) that the current project is up for deprecation / change of maintainer / (or simply) unmaintained and, as a recommendation point readers to switch to another package such as https://github.com/davesque/django-rest-framework-simplejwt. This package is also mentioned in the official documentation of Django Rest Framework (https://www.django-rest-framework.org/api-guide/authentication/#json-web-token-authentication).

[superandrew]

I've used both in many projects and I can confirm that in small to mid sized projects it is not too much of a hassle to switch from one to another.

[bangpradyumna]

We are currently using this library. The link for documentation is broken (GetBlimp). Please fix it to point to the place where docs are currently residing

[jpadilla]

I would recommend, to mention in the top of the readme (and thus also op PyPI) that the current project is up for deprecation / change of maintainer / (or simply) unmaintained and, as a recommendation point readers to switch to another package such as https://github.com/davesque/django-rest-framework-simplejwt. This package is also mentioned in the official documentation of Django Rest Framework (https://www.django-rest-framework.org/api-guide/authentication/#json-web-token-authentication).

@jberends Done, thanks.

[AviKKi]

@bangpradyumna same here, you can read docs here
while they fix it.

[jpadilla]

http://jpadilla.github.io/django-rest-framework-jwt/

[joseph-fox]

@jpadilla, I am the maintainer of https://github.com/joseph-fox/python-bloomfilter. I have used your package in a few projects, and I am happy to help to maintain your package.

[ivlevdenis]

Ping @jazzband

[leni1]

So according to this issue it would seem that the fork of this repository is the best solution for now since django-rest-framework-simplejwt is also looking for maintainers.

[davesque]

@leni1 I haven't had much time lately to maintain it but I haven't thrown in the towel yet! :)

I've recruited a few active community members recently to help with triaging issues. Hopefully, I'll also be able to hand off PR review and merging duties soon.