#28089: Remove requirement of get_short_name and get_full_name for subclasses of
AbstractBaseUser
-------------------------------------+-------------------------------------
Reporter: Josh Schneier | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: contrib.auth | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Josh Schneier):
Currently in `AbstractBaseUser` they raise `NotImplementedError`, I would
remove those definitions.
Actually what do you think of simply removing `get_short_name` and
`get_full_name` altogether? They feel like legacy warts to me given the
custom user model. We can just use the `__str__` of the user where
appropriate (currently `get_username()` everywhere).
--
Ticket URL: <https://code.djangoproject.com/ticket/28089#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 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.3ddd3a85f17b221a9361c316229340d4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
