Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#17539 closed Cleanup/optimization (wontfix)

django-admin.py collectstatic is invalid

Reported by: tskarthikus@… Owned by: Matt Seymour
Component: Documentation Version: 1.3
Severity: Normal Keywords: django-admin.py collectstatic
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

The "django-admin.py collectstatic" command should be replaced with this command.
"python manage.py collectstatic"

Attachments (1)

bug.png (112.2 KB ) - added by anonymous 12 years ago.

Download all attachments as: .zip

Change History (4)

by anonymous, 12 years ago

Attachment: bug.png added

comment:1 by Matt Seymour, 12 years ago

Cc: Matt Seymour added
Owner: changed from nobody to Matt Seymour
Triage Stage: UnreviewedAccepted

comment:2 by anonymous, 12 years ago

Resolution: wontfix
Status: newclosed

These 'django-admin.py <command name>' titles in the documentation are generated automatically (with a custom role for the Sphinx tool) starting from the <command name> value. It was decided back then that such facility would prefix it with 'django-admin.py '.

Because of this, all the management commands in that document have with such a title even those commands whose execution would make more sense in the context of an existing project i.e. it is easier to invoke them by using manage.py (e.g. collectstatic, startapp, syncdb, runserver, ...)

This isn't wrong because, as the notes at the top of such document describe, it is possible to use these management commands by invoking django-admin.py with the --settings switch or by specifying the DJANGO_SETTINGS_MODULE environment variable. Also, these notes include this paragraph:

The command-line examples throughout this document use django-admin.py to be consistent, but any example can use manage.py just as well.

comment:3 by Matt Seymour, 12 years ago

Cc: Matt Seymour removed
Type: BugCleanup/optimization
Note: See TracTickets for help on using tickets.
Back to Top