Opened 18 years ago

Closed 18 years ago

#2299 closed defect (wontfix)

[patch] Settings is loaded as a file rather than a module when using

Reported by: john@… Owned by: Adrian Holovaty
Component: Core (Management commands) Version: magic-removal
Severity: normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


If my settings are not in a file nameed which is the same directory as, django/core/ complains.

Patch changes to take the absolute filename of, the name of the settings module and works out the correct paths and modules. The patch also changes the default to send the correct path to execute_manager.

Settings can also be in (which is where I first started to see this issue).

Attachments (1)

manage-settings.diff (1.4 KB ) - added by john@… 18 years ago.
Patch for this ticket.

Download all attachments as: .zip

Change History (2)

by john@…, 18 years ago

Attachment: manage-settings.diff added

Patch for this ticket.

comment:1 by Adrian Holovaty, 18 years ago

Resolution: wontfix
Status: newclosed

I'm marking this as a wontfix because we're fine with the constraint that assumes the settings file is called To use Django with another settings file, just use --settings.

Note: See TracTickets for help on using tickets.
Back to Top