#28089: Remove requirement of get_short_name and get_full_name for subclasses of
AbstractBaseUser
-----------------------------------------+------------------------
Reporter: Josh Schneier | Owner: nobody
Type: Uncategorized | Status: new
Component: contrib.auth | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------
Since `USERNAME_FIELD` became required and the corresponding
`get_username` now always exists it doesn't make much sense to me to
require the implementation of these 2 methods. They are only used once
each in fairly inconsequential parts of the admin (history in addition to
username for `get_full_name` and the greetings in the header block for
`get_short_name`). All other methods are concrete and generally
applicable. I do think we should still leave them in `AbstractUser`.
--
Ticket URL: <https://code.djangoproject.com/ticket/28089>
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/052.5679a9cd5bb0dca733ab853aaccf242d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
