#19901: introspect user model to determine REQUIRED_FIELDS
--------------------------------------+------------------------------------
Reporter: ptone | Owner:
Type: Cleanup/optimization | Status: new
Component: contrib.auth | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by biern):
This would require writing new metaclass for AbstractBaseUser which would
not work in master currently (see #19688). Also, I think that this might
be misleading and would have a limited usability, since ie, it would
include fields that are required, but automatically set in save method.
--
Ticket URL: <https://code.djangoproject.com/ticket/19901#comment:4>
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.
For more options, visit https://groups.google.com/groups/opt_out.
