manage.py throws away exception information

[Leo Shklovskii]

When an ImportError occurs in manage.py, the exception is caught and stored in a variable - e, but that data isn't used in the error message at all.

Because settings.py is a python file, there could be a variety of issues that come up and its useful to see what the actual underlying error is. In my usecase, I have the line

from settings_local import *

at the end of the main settings.py file. If settings_local.py doesn't exist, then an import error gets thrown but the exception handling in manage.py swallows it. It would be great to add something like:

sys.stderr.write(e.message + '\n')

to manage.py to surface the actual error that's occurring.

[Graham King]

Looks like a duplicate of #14130. Please re-open if I'm mistaken.

Either way, the problem is gone. I've tried every which way I can think to cause an error in settings.py (import errors, regular errors, file permission errors deep within the logging module, etc) and it always gets reported correctly to the console.

[Leo Shklovskii]

Thanks Graham. It is a dup and it's all fixed.