manage.py throws away exception information
|Reported by:||Leo Shklovskii||Owned by:||nobody|
|Cc:||Triage Stage:||Design decision needed|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
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.
Change History (7)
comment:1 Changed 7 years ago by
|Patch needs improvement:||unset|
|Triage Stage:||Unreviewed → Design decision needed|