#23321: Remove .mo files from the Django Git repository
-------------------------------------+-------------------------------------
Reporter: Claude Paroz | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: | Version: dev
Internationalization |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Someday/Maybe
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Ningú):
Replying to [comment:13 Natalia Bidart]:
> Claude, question: in your PR, why are you favoring using `msgfmt`
directly instead of using the Django `compilemessages` command (perhaps
its internal `compile_messages` helper)?
At the time I experimented my build-system requirement idea on a third
party package (but didn't push it forward): https://github.com/farridav
/django-jazzmin/pull/526/commits/d0ff328a46b21410c491a7daf6d92c0c44c88543
While using Django's compilemessages was convenient, it already felt weird
to use django as a build dependency because I felt porting this approach
to Django itself would be sort of a red flag (I couldn't build django
because I'd require django having been built?). Claude's msgfmt felt
unfamiliar but the right way nonetheless.
Also agree on all points made by Natalia Bidart, specially Babel adoption
being an orthogonal issue.
--
Ticket URL: <https://code.djangoproject.com/ticket/23321#comment:15>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018cd9983397-8d64f140-819a-404a-b3b8-42283d5f2f63-000000%40eu-central-1.amazonses.com.
