#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: assigned
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
-------------------------------------+-------------------------------------
Comment (by Mikhail Porokhovnichenko):
Seems to be done. Can be reviewed
[https://github.com/marazmiki/django/tree/ticket_29132 here]
--
Ticket URL: <https://code.djangoproject.com/ticket/29132#comment:6>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.1c3c090e883494bc60bd0eb85a5d0260%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
