Opened 18 years ago
Closed 18 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: | dev | 
| 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: | no | UI/UX: | no | 
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 by , 18 years ago
| Component: | Documentation → django-admin.py | 
|---|---|
| Owner: | changed from to | 
| Summary: | tutorial: manage.py validate example shows extra parameter → manage.py validate no longer accepts application name as an argument | 
| Triage Stage: | Unreviewed → Design decision needed | 
comment:2 by , 18 years ago
| Resolution: | → fixed | 
|---|---|
| Status: | new → closed | 
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.