Opened 17 years ago
Closed 17 years ago
#6102 closed (wontfix)
setup_environ() should preserve DJANGO_SETTINGS_MODULE as-is
Reported by: | Etienne Robillard | Owned by: | Etienne Robillard |
---|---|---|---|
Component: | Core (Other) | Version: | dev |
Severity: | Keywords: | setup_environ, call_command, management | |
Cc: | Triage Stage: | Ready for checkin | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Attached is a patch for setup_environ(). This method should allow users to
use a arbitrary settings module/package from sys.path, thus preserving the ability
to overrides any app-specific settings.
Attachments (1)
Change History (4)
by , 17 years ago
Attachment: | setup_environ.diff added |
---|
comment:1 by , 17 years ago
Status: | new → assigned |
---|
comment:2 by , 17 years ago
Triage Stage: | Unreviewed → Ready for checkin |
---|
comment:3 by , 17 years ago
Resolution: | → wontfix |
---|---|
Status: | assigned → closed |
No, I think this would be a bit of a dangerous change, since it would leave the environment variable and the settings in use out of synchronisation and that will lead to difficult to reproduce bugs. If your code uses the environment variable, you should make sure to call setup_environ() with the value of the environment variable.
initial revision