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

[john@…]

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).

[john@…]

Patch for this ticket.

[Adrian Holovaty]

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.