Opened 9 years ago

Closed 9 years ago

#2299 closed defect (wontfix)

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

Reported by: john@… Owned by: adrian
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: UI/UX:

Description

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

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

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

Attachments (1)

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

Download all attachments as: .zip

Change History (2)

Changed 9 years ago by john@…

Patch for this ticket.

comment:1 Changed 9 years ago by adrian

  • Resolution set to wontfix
  • Status changed from new to closed

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

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