Code

Opened 7 years ago

Closed 7 years ago

#4581 closed (invalid)

Typo - oldforms should be newforms

Reported by: anonymous Owned by: jacob
Component: Documentation Version: master
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description (last modified by mtredinnick)

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

Attachments (0)

Change History (1)

comment:1 Changed 7 years ago by mtredinnick

  • Description modified (diff)
  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to invalid
  • Status changed from new to closed

(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).

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.