settings_envvar and OptionParser behave differently

[dmr]

With

def main(): run_app(settings_initializer='MY_CONF', ...)

When I call

MY_CONF="my.py" my test --stop

everything works fine but with

my --config=my.py test --stop

I get a no option "--stop" error. (I'm using the nose test runner)

Is that behavior expected?

Can the --config option be removed?
The settings_envvar could be assumed to be there on start and that would also provide another benefit:
When I initialize a new project I had to look into the code until I realized that "my init" required another parameter: the default config path --> If the settings_envvar would be required the error would be more clear I think.

[dcramer]

This sounds odd for sure.

I actually do sort of agree. --config is pretty over complicated, and in retrospect not that useful. I think having a path to initialize the config is useful, but we only use env vars for everything these days.