#35530: `django.contrib.auth.login` inconsistently guards `request.user`
-------------------------------------+-------------------------------------
Reporter: Jaap Roes | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: contrib.auth | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jaap Roes):
* has_patch: 0 => 1
* resolution: invalid =>
* status: closed => new
Comment:
I've decided to deprecate the `request.user` fallback path (see linked
PR). If anyone depends on this behaviour it should be possible to migrate
to a pattern where login is called with a user, instead of setting it on
the request and calling login without one.
--
Ticket URL: <https://code.djangoproject.com/ticket/35530#comment:5>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701904950bb06-b0c65879-5517-435a-892e-0aef869dfe19-000000%40eu-central-1.amazonses.com.
