#24384: compilemessages shouldn't return with exit code 0 when it fails
-------------------------------------+-------------------------------------
Reporter: aaugustin | Owner: nobody
Type: Bug | Status: new
Component: | Version: master
Internationalization |
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
-------------------------------------+-------------------------------------
Comment (by claudep):
The reason of the current behaviour is that `compilemessages` run
`compile_messages` for all paths of `settings.LOCALE_PATHS`. The idea was
to not stop running the command if only one path is read-only but not the
others. When #24159 will be fixed, it's probable that `compile_messages`
will be launched for all apps in `INSTALLED_APPS`. Then we don't want to
fail when some app is read-only (maybe a third-party app in a non-readable
location).
--
Ticket URL: <https://code.djangoproject.com/ticket/24384#comment:1>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.ee8dfd6340aa3cca6fd8d9b0c3172ad4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
