Opened 5 years ago

Closed 5 years ago

#21433 closed Uncategorized (duplicate)

Stupid error handling in translation which block to solve error :)

Reported by: anonymous Owned by: nobody
Component: Internationalization Version: 1.5
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


See this code:

if status != STATUS_OK:

raise CommandError(

"errors happened while running msgmerge\n%s" % errors)

Why we delete invalid *.pot file - how to find error after it?

This file should be save for analysis!

Change History (1)

comment:1 Changed 5 years ago by Baptiste Mispelon

Resolution: duplicate
Status: newclosed


Please choose your words more carefully when opening a ticket (Django is made by volunteer contributors, none of which would appreciate being called "stupid") [1].

As for your issue, it's already been reported in #17008. You'll note that this ticket has been fixed and made it to the 1.6 release.


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