mirror of
https://github.com/django/django.git
synced 2025-08-04 19:08:28 +00:00
Always use parentheses when documenting a method with no arguments.
This commit is contained in:
parent
79e1d6ebd7
commit
05d36dc06e
11 changed files with 36 additions and 36 deletions
|
@ -396,7 +396,7 @@ a form object, and each rendering method returns a Unicode object.
|
|||
``as_p()``
|
||||
~~~~~~~~~~
|
||||
|
||||
.. method:: Form.as_p
|
||||
.. method:: Form.as_p()
|
||||
|
||||
``as_p()`` renders the form as a series of ``<p>`` tags, with each ``<p>``
|
||||
containing one field::
|
||||
|
@ -413,7 +413,7 @@ containing one field::
|
|||
``as_ul()``
|
||||
~~~~~~~~~~~
|
||||
|
||||
.. method:: Form.as_ul
|
||||
.. method:: Form.as_ul()
|
||||
|
||||
``as_ul()`` renders the form as a series of ``<li>`` tags, with each
|
||||
``<li>`` containing one field. It does *not* include the ``<ul>`` or
|
||||
|
@ -432,7 +432,7 @@ flexibility::
|
|||
``as_table()``
|
||||
~~~~~~~~~~~~~~
|
||||
|
||||
.. method:: Form.as_table
|
||||
.. method:: Form.as_table()
|
||||
|
||||
Finally, ``as_table()`` outputs the form as an HTML ``<table>``. This is
|
||||
exactly the same as ``print``. In fact, when you ``print`` a form object,
|
||||
|
@ -864,7 +864,7 @@ form data *and* file data::
|
|||
Testing for multipart forms
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. method:: Form.is_multipart
|
||||
.. method:: Form.is_multipart()
|
||||
|
||||
If you're writing reusable views or templates, you may not know ahead of time
|
||||
whether your form is a multipart form or not. The ``is_multipart()`` method
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue