#19901: introspect user model to determine REQUIRED_FIELDS
--------------------------------------+------------------------------------
Reporter: ptone | Owner:
Type: Cleanup/optimization | Status: closed
Component: contrib.auth | Version: master
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by ptone):
* status: new => closed
* resolution: => wontfix
Comment:
While I'm not sure the metaclass needs to be involved, you are right that
required fields which are set in custom save methods are near impossible
to differentiate from those that need to be prompted for - so I'm closing
this for now until some bolt of brilliance might hit someone - thanks for
looking at it.
--
Ticket URL: <https://code.djangoproject.com/ticket/19901#comment:5>
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.
