MENU
forms.Form.as_p()
  • References/Python/Django/API/Forms/The Forms API

Form.as_p() as_p() renders the form as a series of <p> tags, with each <p>

2025-01-10 15:47:30
forms.BoundField.errors
  • References/Python/Django/API/Forms/The Forms API

BoundField.errors A list-like object that is displayed as an HTML <ul class="errorlist">

2025-01-10 15:47:30
forms.BoundField.as_hidden()
  • References/Python/Django/API/Forms/The Forms API

BoundField.as_hidden(attrs=None, **kwargs) [source] Returns a string of HTML for representing

2025-01-10 15:47:30
forms.Form.auto_id
  • References/Python/Django/API/Forms/The Forms API

Form.auto_id By default, the form rendering methods include: HTML id

2025-01-10 15:47:30
forms.Form.cleaned_data
  • References/Python/Django/API/Forms/The Forms API

Form.cleaned_data Each field in a Form class is responsible not only for validating data, but also for “cleaning”

2025-01-10 15:47:30
forms.Form.fields
  • References/Python/Django/API/Forms/The Forms API

Form.fields You can access the fields of Form instance from its fields attribute:

2025-01-10 15:47:30
forms.BoundField.css_classes()
  • References/Python/Django/API/Forms/The Forms API

BoundField.css_classes() [source] When you use Django’s rendering shortcuts, CSS classes

2025-01-10 15:47:30
forms.Form.order_fields()
  • References/Python/Django/API/Forms/The Forms API

Form.order_fields(field_order) New in Django 1.9. You

2025-01-10 15:47:30
forms.BoundField.html_name
  • References/Python/Django/API/Forms/The Forms API

BoundField.html_name The name that will be used in the widget’s HTML name attribute. It takes the form prefix

2025-01-10 15:47:30
forms.BoundField.label_tag()
  • References/Python/Django/API/Forms/The Forms API

BoundField.label_tag(contents=None, attrs=None, label_suffix=None) [source] To separately

2025-01-10 15:47:30