documentation: django-admin.py and manage.py: createsuperuser

[anonymous]

Once a site has been created and syncdb has been run, if the option to create a superuser is initially rejected, it cannot be created by using "django-admin.py createsuperuser". Instead, "manage.py createsuperuser" must be used. This isn't clear from the documentation.

[Russell Keith-Magee]

manage.py and django-admin.py are exactly the same command, except that manage.py implies a specific --settings=path.to.settings argument. You can use django-admin.py createsuperuser if you manually specify the --settings=path.to.settings argument.

This relationship is documented right at the start of the ​docs on django-admin.py. If you think this needs to be clarified somewhere else, please provide a specific description of what needs to be improved.