#26986: `force_login` requires `user.is_active` in 1.10
--------------------------------------+------------------------------------
Reporter: Tordek | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.10
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by timgraham):
* easy: 1 => 0
Comment:
Okay, that makes sense but the current documentation proposal isn't
technically correct since `force_login()` already did delegate the
decision to the authentication backend. The issue is rather that the
default authentication backend now rejects inactive users.
Maybe you can propose some other clarification or we can close this ticket
as a misunderstanding?
--
Ticket URL: <https://code.djangoproject.com/ticket/26986#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.483aa4c2f746c5a1599366ce3f3aa8a9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
