#26032 closed Cleanup/optimization (fixed)
Where does `manage.py` belong: to Application or to Project?
Reported by: | Thomas Güttler | Owned by: | nobody |
---|---|---|---|
Component: | Documentation | Version: | 1.9 |
Severity: | Normal | Keywords: | |
Cc: | tzanke@… | Triage Stage: | Unreviewed |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
First: Thanks to Tim Graham for fixing the "app vs project" issue (https://code.djangoproject.com/ticket/25748)
Here is the current part about "application":
The term **application** describes a Python package that provides some set of features. Applications :doc:`may be reused </intro/reusable-apps/>` in various projects. A project's root directory (the one that contains ``manage.py``) is usually the container for all of a project's applications which aren't installed separately.
Where does "manage.py" belong? to Application or to Project?
My personal point of view is that it belongs to "project", since there can only be one script with this name.
I think the above part in the docs needs to be improved. Maybe just move the sentence to the previous part.
Change History (6)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
Hmmm chicken-egg problem. I like the dictionary style:
A: ... definition of A
B: ... definition of B.
I think forward references are ok.
comment:6 by , 9 years ago
Cc: | added |
---|
We could move it as you suggest, but I thought it makes sense to introduce what an application is before discussing them (such as where they are located) in much detail. Does anyone else find the current version unclear?