#29132: update_last_login signal handler shouldn't be connected if
User.last_login
attribute isn't a field
-------------------------------------+-------------------------------------
Reporter: Mikhail | Owner: nobody
Porokhovnichenko |
Type: Bug | Status: new
Component: contrib.auth | Version: 2.0
Severity: Normal | Resolution:
Keywords: last_login, | Triage Stage: Accepted
update_last_login, signals, |
user_logged_in |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* stage: Unreviewed => Accepted
Comment:
I was thinking that `isinstance(... Field)` might be incorrect if
`last_login` was a settable property, but in that case, I guess
`user.save(update_fields['last_login'])` probably wouldn't be desired.
--
Ticket URL: <https://code.djangoproject.com/ticket/29132#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/067.c5e5ea6412aa5100a94d4d90e200378d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
