Re: [Django] #22616: CommandError exception no prints message - instead always is "django.core.management.base.CommandError"

[Django]

#22616: CommandError exception no prints message - instead always is
"django.core.management.base.CommandError"
---+--
 Reporter:  Cezary.Wagner  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.6
 Severity:  Normal |   Resolution:  worksforme
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timo):

 * status:  new => closed
 * resolution:   => worksforme


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.103ad2d1cd687dd2c9fa8bf3c2696a1b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22616: CommandError exception no prints message - instead always is "django.core.management.base.CommandError"

[Django]

#22616: CommandError exception no prints message - instead always is
"django.core.management.base.CommandError"
---+--
 Reporter:  Cezary.Wagner  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Old description:

> 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

New description:

 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

--

Comment (by timo):

 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.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.2941b68bc6f55e8a123d18d84da2219b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22616: CommandError exception no prints message - instead always is "django.core.management.base.CommandError"

[Django]

#22616: CommandError exception no prints message - instead always is
"django.core.management.base.CommandError"
---+--
 Reporter:  Cezary.Wagner  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Cezary.Wagner):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Fix exception to produce message.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.c8840b3ce19c6e3f0b8626b1cb208f44%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22616: CommandError exception no prints message - instead always is "django.core.management.base.CommandError"

[Django]

#22616: CommandError exception no prints message - instead always is
"django.core.management.base.CommandError"
---+
 Reporter:  Cezary.Wagner  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 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

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/056.82452ee522b46b9399b64b43ce23f395%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.