#25156 closed Cleanup/optimization (fixed)
Settings overview should mention django.setup() is needed for "standalone" Django use
| Reported by: | James Bennett | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | yes | UI/UX: | no |
Description
Since that's the main place people seem to go to find information on manually configuring settings for standalone use, it should mention that django.setup() now has to be called as part of that process, in addition to settings.configure().
In fact, what it really should have is a section on how to configure Django to run standalone (i.e., not in a web server context).
Change History (4)
comment:1 by , 9 years ago
| Easy pickings: | set |
|---|---|
| Needs documentation: | unset |
| Triage Stage: | Unreviewed → Accepted |
| Type: | Uncategorized → Cleanup/optimization |
comment:2 by , 9 years ago
| Has patch: | set |
|---|---|
| Triage Stage: | Accepted → Ready for checkin |
Note:
See TracTickets
for help on using tickets.
PR