Opened 15 years ago
Closed 14 years ago
#13043 closed New feature (duplicate)
Default manage.py should print ImportError
Reported by: | sdolan | Owned by: | nobody |
---|---|---|---|
Component: | Core (Management commands) | Version: | 1.2-beta |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | yes |
Easy pickings: | no | UI/UX: | no |
Description
Problem
The error handling in the default manage.py for an ImportError is difficult/frustrating to debug if the error was not in importing the settings module itself.
Solution
Print out the ImportError exception when it occurs. The ImportError exception gives details of the actual module that failed to import.
Attachments (2)
Change History (10)
by , 15 years ago
Attachment: | 13043__print_exception_in_default_manage_settings_import.patch added |
---|
comment:1 by , 15 years ago
milestone: | 1.2 |
---|
follow-up: 3 comment:2 by , 15 years ago
Triage Stage: | Unreviewed → Accepted |
---|
This is something that falls in the general category of BetterErrorMessages.
by , 15 years ago
Attachment: | 13043__alternate_approach_with_more_info.patch added |
---|
comment:3 by , 15 years ago
Replying to russellm:
This is something that falls in the general category of BetterErrorMessages.
Something similar was also requested in ticket:10696
I also attached an alternate approach that attempts to give more information like the traceback. It also passes pylint with a perfect score.
comment:4 by , 14 years ago
Type: | → New feature |
---|
comment:5 by , 14 years ago
Severity: | → Normal |
---|
comment:6 by , 14 years ago
Easy pickings: | unset |
---|---|
Patch needs improvement: | set |
13043alternate_approach_with_more_info.patch fails to apply cleanly on to trunk
comment:7 by , 14 years ago
Component: | Uncategorized → Core (Management commands) |
---|---|
UI/UX: | unset |
comment:8 by , 14 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
duplicate of #14130 (that is newer, but is already fixed)
This isn't anywhere near critical enough to go on the 1.2 milestone.