Django/django
11
0
Fork 0
Code Pull Requests Projects Releases Activity

[1.5.x] Fixed #20248 - Clarified manage.py vs. django-admin.py

Browse Source 
Backport of 8fc68af9c0 from master
This commit is contained in:
Tim Graham 2013-04-12 06:10:26 -04:00
parent 9c49e64b66
commit 8ab5db7a33
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/ref/django-admin.txt
View File

@ -25,9 +25,10 @@ copy ``django-admin.py`` to a location on your existing path or edit the
Environment...``) to point to its installed location. Environment...``) to point to its installed location.
Generally, when working on a single Django project, it's easier to use Generally, when working on a single Django project, it's easier to use
``manage.py``. Use ``django-admin.py`` with ``DJANGO_SETTINGS_MODULE``, or the ``manage.py`` than ``django-admin.py``. If you need to switch between multiple
``--settings`` command line option, if you need to switch between multiple Django settings files, use ``django-admin.py`` with
Django settings files. :envvar:`DJANGO_SETTINGS_MODULE` or the :djadminopt:`--settings` command line
option.
The command-line examples throughout this document use ``django-admin.py`` to The command-line examples throughout this document use ``django-admin.py`` to
be consistent, but any example can use ``manage.py`` just as well. be consistent, but any example can use ``manage.py`` just as well.