From bfc5660c472ac2e52cc4fdec78315c87b01357de Mon Sep 17 00:00:00 2001 From: Joseph Kocherhans Date: Thu, 13 Mar 2008 06:14:26 +0000 Subject: newforms-admin: Merged from trunk up to [7232] git-svn-id: http://code.djangoproject.com/svn/django/branches/newforms-admin@7233 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/newforms.txt | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'docs/newforms.txt') 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, -- cgit v1.3