[Django] #30720: allow specifying multiple domains for makemessages and compilemessages commands

7 views
Skip to first unread message

Django

unread,
Aug 21, 2019, 8:38:41 AM8/21/19
to django-...@googlegroups.com
#30720: allow specifying multiple domains for makemessages and compilemessages
commands
------------------------------------------------+------------------------
Reporter: c v t | Owner: nobody
Type: New feature | Status: new
Component: Internationalization | Version: 2.2
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 0 |
------------------------------------------------+------------------------
(The left-over part of #17181..)

Currently, to update / compile catalogues for both `django` and `djangojs`
domains, you need to run `makemessages` and `compilemessages` twice:

django-admin.py makemessages -d django
django-admin.py makemessages -d djangojs

It would be lovely to be able to run this in one command, either:

django-admin.py makemessages -d django,djangojs

or:

django-admin.py makemessages -d django -d djangojs

(Currently, the first version gives an error; the second version silently
ignores the first `-d` option, in this example it would just regenerate
`djangojs`)

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

Django

unread,
Aug 21, 2019, 11:46:30 AM8/21/19
to django-...@googlegroups.com
#30720: allow specifying multiple domains for makemessages and compilemessages
commands
-------------------------------------+-------------------------------------

Reporter: c v t | Owner: nobody
Type: New feature | Status: new
Component: | Version: 2.2
Internationalization |
Severity: Normal | Resolution:

Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Claude Paroz):

Apparently this was abandoned as per
https://code.djangoproject.com/ticket/17181#comment:9. It may be that the
current code allows an easier implementation. We would have to see a patch
to judge that. Do you plan to provide one?

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

Django

unread,
Aug 22, 2019, 5:32:52 AM8/22/19
to django-...@googlegroups.com
#30720: allow specifying multiple domains for makemessages and compilemessages
commands
-------------------------------------+-------------------------------------

Reporter: c v t | Owner: nobody
Type: New feature | Status: new
Component: | Version: 2.2
Internationalization |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by dheeru0198):

* cc: dheeru0198 (added)


--
Ticket URL: <https://code.djangoproject.com/ticket/30720#comment:2>

Django

unread,
Aug 23, 2019, 3:20:25 AM8/23/19
to django-...@googlegroups.com
#30720: Allow specifying multiple domains for makemessages command.
-------------------------------------+-------------------------------------

Reporter: c v t | Owner: nobody
Type: New feature | Status: closed
Component: | Version: master
Internationalization |
Severity: Normal | Resolution: wontfix

Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by felixxm):

* status: new => closed
* version: 2.2 => master
* resolution: => wontfix
* easy: 1 => 0


Comment:

Thanks for this ticket.

`compilemessages` doesn't have `domain` argument.

Supporting multiple domains in `makemessages` can still be clunky, because
they handle different extensions etc. It's probably not worth to add a
complexity here.
Closing for now, nevertheless, if you would like to provide a patch we can
evaluate it and reopen the ticket if consensus is reached.

--
Ticket URL: <https://code.djangoproject.com/ticket/30720#comment:3>

Reply all
Reply to author
Forward
0 new messages