Opened 12 years ago
Closed 12 years ago
#19079 closed Cleanup/optimization (fixed)
make USERNAME_FIELD a required attribute of user objects
| Reported by: | Preston Holmes | Owned by: | nobody |
|---|---|---|---|
| Component: | contrib.auth | Version: | dev |
| Severity: | Release blocker | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
currently it is documented as required, but is not present in any base class
instead a number of places we fall back to looking for a 'username' attribute
per:
https://code.djangoproject.com/ticket/19077#comment:6
it would clean things up a bit to simply require this as a defined attribute, and represent it appropriately on the base classes
Change History (2)
comment:1 by , 12 years ago
| Severity: | Normal → Release blocker |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
comment:2 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
I've got a patch to address this almost ready to go.