--
Ticket URL: <https://code.djangoproject.com/ticket/18261>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* needs_better_patch: => 0
* needs_docs: => 0
* needs_tests: => 0
* stage: Unreviewed => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/18261#comment:1>
Comment (by carljm):
I'm not familiar enough with the i18n toolchain to be sure where
compilemessages/makemessages should be run, or why it would work in one
place but not another, but we should _not_ document that `mysite/mysite`
is the "project root directory". The latter is a confusing term that we
should maybe just avoid using; if it should have any meaning, it should
mean "the directory with `manage.py`", which would be just `mysite/`. The
inner directory is the "project module", the outer directory could be
called the "workspace" or "container" or "project root".
In general, we want people running most command-line stuff in the
workspace directory (the one with manage.py), because that will set up
sys.path correctly for all their imports to work. This may not apply to
compilemessages/makemessages though.
--
Ticket URL: <https://code.djangoproject.com/ticket/18261#comment:2>
* has_patch: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/18261#comment:4>
Comment (by loic84):
FWIW the new default `settings.py` refers to that directory as `BASE_DIR`.
I wasn't a big fan of the `BASE_DIR` wording (I prefer `PROJECT_ROOT`) but
now that it's there maybe we should refer to that directory as the "base
directory".
--
Ticket URL: <https://code.djangoproject.com/ticket/18261#comment:5>
Comment (by timo):
Could someone familiar with `makemessages` confirm where it should be run
from? I'd expect "project root" means the directory with `manage.py` but
based on what the reporters says, it seems like that directory didn't work
for him. I've edited Susan's patch slightly, but it'll need further edits
if the existing "project root" reference in translation.txt actually means
"project module".
--
Ticket URL: <https://code.djangoproject.com/ticket/18261#comment:6>
Comment (by aaugustin):
AFAIK `makemessages` must be run from a directory that contains a
`locale/` subdirectory where the translations will be collected. `locale/`
can be anywhere as long as it's in `LOCALE_PATHS`.
Django does *not* have a concept of a "project root", no matter how you
frame it.
--
Ticket URL: <https://code.djangoproject.com/ticket/18261#comment:7>
* status: new => assigned
* owner: nobody => susan
--
Ticket URL: <https://code.djangoproject.com/ticket/18261#comment:8>
Comment (by susan):
See PR: https://github.com/django/django/pull/1340/ Feel free to code
review there.
--
Ticket URL: <https://code.djangoproject.com/ticket/18261#comment:9>
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"ef3fddf26e8bfe956a52c2aa678db6637caf7adf"]:
{{{
#!CommitTicketReference repository=""
revision="ef3fddf26e8bfe956a52c2aa678db6637caf7adf"
Fixed #18261 -- Clarified 'project root directory'
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/18261#comment:10>
Comment (by Tim Graham <timograham@…>):
In [changeset:"5192dbbf5546eb62e1c24d36d91f270b1a2b5eaf"]:
{{{
#!CommitTicketReference repository=""
revision="5192dbbf5546eb62e1c24d36d91f270b1a2b5eaf"
[1.5.x] Fixed #18261 -- Clarified 'project root directory'
Backport of ef3fddf26e from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/18261#comment:11>