Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#27361 closed Cleanup/optimization (fixed)

Use "from django import forms" in forms api examples

Reported by: Zach Borboa Owned by: nobody
Component: Documentation Version: dev
Severity: Normal Keywords:
Cc: Triage Stage: Ready for checkin
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by Tim Graham)

It's more common to define forms using a style like:

from django import forms

class PersonForm(forms.Form):
   first_name = forms.CharField()

than from django.forms import Form, CharField.

Change History (5)

comment:1 by Zach Borboa, 9 years ago

Description: modified (diff)

PR ​https://github.com/django/django/pull/7407

comment:2 by Zach Borboa, 9 years ago

Description: modified (diff)

comment:3 by Tim Graham, 9 years ago

Component: Uncategorized → Documentation
Description: modified (diff)
Summary: Small clean up on forms api documentation → Use "from django import forms" in forms api examples
Triage Stage: Unreviewed → Ready for checkin

comment:4 by Tim Graham <timograham@…>, 9 years ago

Resolution: → fixed
Status: new → closed

In 90c3b11e:

Fixed #27361 -- Used "from django import forms" in forms api docs.

comment:5 by Tim Graham <timograham@…>, 9 years ago

In 3f73045:

[1.10.x] Fixed #27361 -- Used "from django import forms" in forms api docs.

Backport of 90c3b11e873a326219a68c14a3b5dca0181e7b3c from master

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