Opened 11 years ago
Closed 11 years ago
#22616 closed Uncategorized (worksforme)
CommandError exception no prints message - instead always is "django.core.management.base.CommandError"
| Reported by: | Cezary.Wagner | Owned by: | nobody |
|---|---|---|---|
| Component: | Uncategorized | Version: | 1.6 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
Example on useless message for makemessages.py
if errors:
if status != STATUS_OK:
raise CommandError(
"errors happened while running msgmerge\n%s" % errors)
This always gives:
django.core.management.base.CommandError
Should:
"errors happened while running msgmerge\n%s" % errors
Change History (3)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
| Description: | modified (diff) |
|---|
It works for me:
$ python manage.py runserver a b CommandError: Usage is runserver [optional port number, or ipaddr:port]
Can you paste your actual terminal output? Also please use formatting on code blocks; I've added some to the description, thanks.
comment:3 by , 11 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Fix exception to produce message.