-
-
Notifications
You must be signed in to change notification settings - Fork 7k
Fixed Django 2.1 compatibility due to removal of django.contrib.auth.login()/logout() views. #5510
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
Conversation
…login()/logout() views.
@felixxm Awesome! I was going to look into that. Thanks! (Will review fully in daylight) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good
Off hand thought - defer this to December when Django 1.10 is deprecated. That way, the compat check isn't necessary. |
As was said earlier, we shouldn't drop a django version unless it's too complicated. Seems we're still on track with that change aren't we ? |
Yep. Let's have this as is for now. All green Travis 🎉 — that's worth the temporary compat check just for the aesthetic benefits over the autumn. 😃 Thanks @felixxm! |
Unwanted side effect, it may trigger |
I've just opened #5564. |
@edmorley - thanks, we'll continue the discussion over there. |
I thought DRF is compatible with Django 2.1, see encode#5510
Fixed Django 2.1 compatibility due to removal of
django.contrib.auth.login()/logout()
views (see Django documentation 1.11, 2.1).