#24159: compilemessages does not behave the same as makemessages
-------------------------------------+-------------------------------------
Reporter: Matthew Somerville | Owner: Matthew
| Somerville
Type: New feature | Status: closed
Component: | Version: master
Internationalization |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Marcin Nowak):
Hi.
I'm using buildout. Both commands, compilemessages (after #24159 patch)
and makemessages, introduced new issues. They scan all nested directories,
they're reading (makemessages) and creating (compilemessages) files in
external eggs and cloned repositories, even in django itself and unused
but stored on disk packages. There is no possibility to exclude or include
directories to search. And any broken locale file in any package can break
compilation process.
--
Ticket URL: <https://code.djangoproject.com/ticket/24159#comment:13>
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/064.ac13be0f07601f83c7d971da1360a8f5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
