[Django] #21433: Stupid error handling in translation which block to solve error :)

3 views
Skip to first unread message

Django

unread,
Nov 13, 2013, 7:44:53 AM11/13/13
to django-...@googlegroups.com
#21433: Stupid error handling in translation which block to solve error :)
--------------------------------------+--------------------
Reporter: anonymous | Owner: nobody
Type: Uncategorized | Status: new
Component: Internationalization | Version: 1.5
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+--------------------
See this code:
if status != STATUS_OK:
os.unlink(potfile)
raise CommandError(
"errors happened while running msgmerge\n%s" % errors)

Why we delete invalid *.pot file - how to find error after it?
os.unlink(potfile)

This file should be save for analysis!

--
Ticket URL: <https://code.djangoproject.com/ticket/21433>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Nov 13, 2013, 8:55:42 AM11/13/13
to django-...@googlegroups.com
#21433: Stupid error handling in translation which block to solve error :)
-------------------------------------+-------------------------------------
Reporter: anonymous | Owner: nobody
Type: Uncategorized | Status: closed
Component: | Version: 1.5
Internationalization | Resolution: duplicate
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by bmispelon):

* status: new => closed
* needs_better_patch: => 0
* resolution: => duplicate
* needs_tests: => 0
* needs_docs: => 0


Comment:

Hi,

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.

[1] https://www.djangoproject.com/conduct/

--
Ticket URL: <https://code.djangoproject.com/ticket/21433#comment:1>

Reply all
Reply to author
Forward
0 new messages