#18261: Clarify the term "project root directory"
-------------------------------------+-------------------------------------
Reporter: schnippi | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: 1.4
Severity: Normal | Resolution:
Keywords: project root, root | Triage Stage: Accepted
directory, translation, | Needs documentation: 0
makemessages, compilemessages | Patch needs improvement: 0
Has patch: 0 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
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>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
