#22652 closed Bug (fixed)
create_superuser in contrib.auth.management expects "objects" manager in 1.7b4
Reported by: | Alex Laird | Owned by: | nobody |
---|---|---|---|
Component: | contrib.auth | Version: | 1.7-beta-2 |
Severity: | Release blocker | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | yes | UI/UX: | no |
Description
We installed Django 1.7b4 to test compatibility with my application and came upon what we believe to be a bug when running our regression tests.
In Django 1.6.5, contrib\auth\management\_init_.py line 116 referes 'created_models' in 'UserModel', but in Django 1.7 this appears to be modified (same file, line 132) to check if UserModel.objects.exists() not. However, we have renamed our user manager to simply "users", so this throws an errors when executed.
Change History (3)
comment:1 by , 10 years ago
Component: | Core (URLs) → contrib.auth |
---|---|
Easy pickings: | set |
Severity: | Normal → Release blocker |
Triage Stage: | Unreviewed → Accepted |
comment:2 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
I guess that simply replacing
objects
by_default_manager
should solve this.