From 0e03d4618be44e02321529814399d8e978d2a184 Mon Sep 17 00:00:00 2001 From: Loic Bistuer Date: Wed, 5 Nov 2014 16:00:22 +0700 Subject: [PATCH] [1.7.x] Removed confusing paragraph from the docs. This snippet wasn't particularly helpful as `add_error()` is described in greater details in the following section. Thanks Claude Paroz for the report. Backport of f1f0c4f16b from master --- docs/ref/forms/validation.txt | 7 ------- 1 file changed, 7 deletions(-) diff --git a/docs/ref/forms/validation.txt b/docs/ref/forms/validation.txt index ea74adb676..3c501440d3 100644 --- a/docs/ref/forms/validation.txt +++ b/docs/ref/forms/validation.txt @@ -328,13 +328,6 @@ write a cleaning method that operates on the ``recipients`` field, like so:: # not. return data -Sometimes you may want to add an error message to a particular field from the -form's :meth:`~Form.clean()` method, in which case you can use -:meth:`~django.forms.Form.add_error()`. Note that this won't always be -appropriate and the more typical situation is to raise a ``ValidationError`` -from , which is turned into a form-wide error that is available through the -:meth:`Form.non_field_errors() ` method. - .. _validating-fields-with-clean: Cleaning and validating fields that depend on each other