Opened 15 years ago

Closed 13 years ago

Last modified 13 years ago

#10696 closed Bug (duplicate)

manage.py throws away exception information

Reported by: Leo Shklovskii Owned by: nobody
Component: Core (Other) Version: dev
Severity: Normal Keywords:
Cc: Triage Stage: Design decision needed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

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 by thatch, 15 years ago

milestone: 1.1
Triage Stage: UnreviewedDesign decision needed

comment:2 by Jacob, 15 years ago

Triage Stage: Design decision neededAccepted

comment:3 by Jacob, 15 years ago

milestone: 1.1

comment:4 by Jacob, 15 years ago

Triage Stage: AcceptedDesign decision needed

comment:5 by Seth Buntin, 13 years ago

Severity: Normal
Type: Bug

comment:6 by Graham King, 13 years ago

Easy pickings: unset
Resolution: duplicate
Status: newclosed

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.

comment:7 by Leo Shklovskii, 13 years ago

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

Note: See TracTickets for help on using tickets.
Back to Top