#22770 closed Cleanup/optimization (fixed)
Remove create_superuser from post_migrate signals
Reported by: | Tim Graham | Owned by: | nobody |
---|---|---|---|
Component: | contrib.auth | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
In IRC, Loic and I were in agreement that the prompt to create a superuser every time after you run migrate
can be annoying. Running createsuperuser
manually is not much of a burden if you do need it. I think we could make the change without a deprecation as it's not clear to me that doing so would offer any benefits.
Change History (6)
comment:1 by , 10 years ago
Has patch: | set |
---|---|
Triage Stage: | Unreviewed → Accepted |
comment:2 by , 10 years ago
If this type of change was proposed by a non core dev, would it even be considered given that 1.7 is already late in the beta stage?
comment:3 by , 10 years ago
I added the logic back to syncdb
for backwards compatibility. Making the change now means we don't have to worry about people expecting the behavior with migrate
.
comment:4 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:6 by , 10 years ago
I created https://github.com/django/django/pull/3143 to address the single remaining documentation straggler.
PR (proposing to include it in 1.7).