#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: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by timgraham):
I don't understand the report. Can you give example code to show the
behavior change? The release note is referring to the removal of the
[https://github.com/django/django/commit/107165c4b04f4e5a830a60b6c66b2e5d8fb1d242
#diff-97160f50594424a40f2621d5a3c581ccL602 user.is_active check in
login()]. As far as I see, `force_login()` isn't affected by that.
--
Ticket URL: <https://code.djangoproject.com/ticket/26986#comment:2>
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.9774ffeb4e80e2a5f20605c5b5461cda%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
