#29132: update_last_login signal handler shouldn't be connected if
User.last_login
attribute isn't a field
-------------------------------------+-------------------------------------
Reporter: Mikhail | Owner: Mikhail
Porokhovnichenko | Porokhovnichenko
Type: Bug | Status: closed
Component: contrib.auth | Version: 2.0
Severity: Normal | Resolution: fixed
Keywords: last_login, | Triage Stage: Ready for
update_last_login, signals, | checkin
user_logged_in |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"14e34dcf8cb935454f4ce02402949d8af204fdab" 14e34dcf]:
{{{
#!CommitTicketReference repository=""
revision="14e34dcf8cb935454f4ce02402949d8af204fdab"
Fixed #29132 -- Avoided connecting update_last_login() handler if
User.last_login isn't a field.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29132#comment:9>
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.2b3170df22cc1877c3cfa3978d841dd3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
