-
Notifications
You must be signed in to change notification settings - Fork 84
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
Compatibility with simplejwt #36
Comments
Hi @anton-shestakov, I was able to reproduce the bug. I think the problem lies much deeper, in the way some of the of the Until the problem will be fixed in DRF I will try to fix it by limiting the imports to bare minimum. Hopefully I will have time today this evening to do this. |
@anton-shestakov I released the fix in version |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Hi @apragacz
First of all, thanks for your work on this nice package. It has minimum set of features and it's just exactly what I need for one of the projects I'm working on.
Now, back to the issue, this package is not compatible with django-rest-framework-simplejwt package which is recommended by django-rest-framework official docs as implementation of JWT authentication.
Problem may also appear with anything that uses django models and specified in rest framework settings (e.g. custom authenticating classes, custom permission classes, etc.). Issue is caused by this line in code triggering all django rest framework settings import while doing checks.
Below is full traceback that appears when I do runserver with following packages installed:
and following django settings (others have default values)
Temporary solution for me is to exclude
rest_registration
fromINSTALLED_APPS
, include views to urlconf and provide required email templates manually. But it would be nice if this was fixed.Thanks,
Anton
The text was updated successfully, but these errors were encountered: