#28247: Don't require last_login property on custom user models
---------------------------------------------+------------------------
Reporter: Linus Lewandowski | Owner: nobody
Type: New feature | Status: new
Component: contrib.auth | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
---------------------------------------------+------------------------
Right now, custom user models are required to provide last_login property
- because django.contrib.auth.models always sets up a user_logged_in
handler that updates this field.
It's trivial to add a try/except that'll make it not required.
--
Ticket URL: <https://code.djangoproject.com/ticket/28247>
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/048.36d820b9c87666a9ee17387aa4b7e9ea%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
