summaryrefslogtreecommitdiff
path: root/docs/newforms.txt
diff options
context:
space:
mode:
Diffstat (limited to 'docs/newforms.txt')
-rw-r--r--docs/newforms.txt6
1 files changed, 5 insertions, 1 deletions
diff --git a/docs/newforms.txt b/docs/newforms.txt
index 33cf48c274..229f704ca7 100644
--- a/docs/newforms.txt
+++ b/docs/newforms.txt
@@ -246,6 +246,10 @@ object::
>>> f.cleaned_data
{'cc_myself': True, 'message': u'Hi there', 'sender': u'foo@example.com', 'subject': u'hello'}
+.. note::
+ **New in Django development version** The ``cleaned_data`` attribute was
+ called ``clean_data`` in earlier releases.
+
Note that any text-based field -- such as ``CharField`` or ``EmailField`` --
always cleans the input into a Unicode string. We'll cover the encoding
implications later in this document.
@@ -1563,7 +1567,7 @@ The three types of cleaning methods are:
Note that any errors raised by your ``Form.clean()`` override will not
be associated with any field in particular. They go into a special
- "field" (called ``__all__``, which you can access via the
+ "field" (called ``__all__``), which you can access via the
``non_field_errors()`` method if you need to.
These methods are run in the order given above, one field at a time. That is,