#22617: Allow to fix translation -> Fix makemessages to not delete debug data
and
hide errors (and all similar modules using "msgmerge")
-------------------------------------+-------------------------------------
Reporter: Cezary.Wagner | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Core (Management | Version: dev
commands) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Ad Timmering):
@Mariusz: Thanks for cc'ing me. Would be happy to add some tests, however
have been unable to replicate the behavior.
Forcably letting `msgmerge` throw errors (by pausing the `makemessages`
process and messing up the intermediate file on purpose), does for me
(a) give sensible error messages, and
(b) they are actually displayed together with the `CommandError`.
I searched SO etc. for other users with similar issues, but unfortunately
couldn't find an example to build a test around.
I suggest closing as `needsinfo`, pending the original author or someone
else to provide an example of a case where the error message given with
the exception does not provide enough information.
Example of an intentionally broken run:
{{{
(env) awtimmering @ ~/djtest $ ./manage.py makemessages --locale nl
processing locale nl
CommandError: errors happened while running msgmerge
/home/awtimmering/djtest/locale/django.pot:49: keyword "msgid_plasdural"
unknown
/home/awtimmering/djtest/locale/django.pot:45: missing 'msgstr' section
/home/awtimmering/djtest/locale/django.pot:49:16: syntax error
msgmerge: found 3 fatal errors
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/22617#comment:15>
Django <https://code.djangoproject.com/>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.8f3c4d36870cfed7d5ba92d55c994527%40djangoproject.com.