Opened 9 years ago

Closed 9 years ago

#5271 closed (fixed)

manage.py validate no longer accepts application name as an argument

Reported by: Pesh Alto Owned by: Adrian Holovaty
Component: Core (Management commands) Version: master
Severity: Keywords: tutorial validate arguments parameters models
Cc: Triage Stage: Design decision needed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

In the tutorial at http://www.djangoproject.com/documentation/tutorial01/
under 'Activating Models', the following example command is given:

python manage.py validate polls — Checks for any errors in the construction of your models.

However, this appears to be out of date. When I run the example as:

python manage.py validate polls

it says that it was given an extra parameter, and that validate takes no parameters.

If I instead run:

python manage.py validate

it appears to work fine. The tutorial should be edited to remove the extra parameter.

Change History (2)

comment:1 Changed 9 years ago by Simon G. <dev@…>

Component: Documentationdjango-admin.py
Owner: changed from Jacob to Adrian Holovaty
Summary: tutorial: manage.py validate example shows extra parametermanage.py validate no longer accepts application name as an argument
Triage Stage: UnreviewedDesign decision needed

I think the question is whether we want to allow validate to take an optional application. This must have been removed in the recent management.py rearrangement.

comment:2 Changed 9 years ago by Russell Keith-Magee

Resolution: fixed
Status: newclosed

(In [6040]) Fixed #5271 -- Fixed documentation reference to using the application name as an argument to manage.py validate. The recent management.py refactor exposed this error; it was silently ignored previously.

Note: See TracTickets for help on using tickets.
Back to Top