Re: [Django] #32145: Unclear error raised by makemessages when /locale does not exist under app directory (was: Error message for missing locale is hard to understand)

[Django]

#32145: Unclear error raised by makemessages when /locale does not exist under app
directory
-------------------------------------+-------------------------------------
Reporter: boxed | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Core (Management | Version: master
commands) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls):

* type: Uncategorized => Cleanup/optimization
* component: Uncategorized => Core (Management commands)
* version: 3.1 => master
* stage: Unreviewed => Accepted

Comment:

Thanks for the report. I agree the message needs to be improved. There
might even be a case for creating `/locale` for the user when we've
detected the user is running `makemessages` in the app directory (which we
already detect), but I would be interested to hear more opinions.

Regarding the command failing silently, I cannot reproduce that. I marked
a string for translation, created the directory `app-level-
directory/locale` and ran `manage.py makemessages -l es` from the app
directory and received translation files. If you suggest providing
feedback to the user when no translatable strings are found that would be
a separate issue.

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