Opened 17 years ago
Closed 17 years ago
#4581 closed (invalid)
Typo - oldforms should be newforms
| Reported by: | anonymous | Owned by: | Jacob |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
http://www.djangoproject.com/documentation/newforms/
in the section describing the old form framework it refers to the two ways of setting up forms .. old and new way
It appears as the sample is wrong using:
from django import oldforms as forms # new
where further down is referred to as:
from django import newforms as forms # new
Change History (1)
comment:1 by , 17 years ago
| Description: | modified (diff) |
|---|---|
| Resolution: | → invalid |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
(Fixed description formatting.)
I can't see where the second comment appears -- searching for "# new" only shows on occurrence in that file. However, the first comment is using the word "new" to contrast with the previous line (which uses the word "old"). It is explaining the difference between the old and new way of using existing (old-) forms.
There isn't any problem here, it's just a matter of context and I think that is clear to the reader (or should be after a short think).