Respect DJANGO_SETTINGS_MODULE, --settings

[anonymous]

I have two settings profiles: one for production (settings) and one for development (settings.dev). I am seeing two problems, which seem related but may be separate:

$ export DJANGO_SETTINGS_MODULE="settings.dev"
$ ./manage.py migrate myapp my_migration

does not use settings.dev. In my case, I'm using a separate database for development. The migration is applied to my production database instead of the development.

./manage.py migrate --settings="settings.dev" ...
Unknown command: 'migrate'

[andrew]

That's odd, South uses the standard Django machinery for configuration. I'll check this.

[andrew]

Using --settings works for me on my dev box; did you forget to include south in settings.dev's installed apps?

[anonymous]

andrew: you were right about south missing from settings.dev.

it looks like my manage.py imports settings (instead of using DJANGO_SETTINGS_MODULE).

therefore, this is invalid as far as I can tell.

[andrew]

Marking as such.