#24780: custom-users-and-signals docs out of date
-------------------------------+--------------------
Reporter: tomviner | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
The [https://docs.djangoproject.com/en/dev/topics/auth/customizing
/#custom-users-and-signals Custom users and signals docs] say:
> Another limitation of custom User models is that you can’t use
django.contrib.auth.get_user_model() as the sender or target of a signal
handler. Instead, you must register the handler with the resulting User
model. See Signals for more information on registering and sending
signals.
Which isn't really helpful, as you can now use the model label, as
mentioned higher on the page:
{{{
post_save.connect(post_save_receiver, sender=settings.AUTH_USER_MODEL)
}}}
So maybe just remove the quoted para? (it was created in
[https://code.djangoproject.com/ticket/19218 this ticket], 2 years ago,
when passing models by label wasn't allowed yet)
Happy to create a patch once we're decided.
--
Ticket URL: <https://code.djangoproject.com/ticket/24780>
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/051.2d96a0ec592e72aefcb63a8996ba5235%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
