Fixed #23151 -- Deprecated RegexField.error_message.

Thanks Baptiste Mispelon for the suggestion.

1 files changed, 7 insertions, 4 deletions

diff --git a/docs/ref/forms/fields.txt b/docs/ref/forms/fields.txt
index e92013a832..7dd0510237 100644
--- a/docs/ref/forms/fields.txt
+++ b/docs/ref/forms/fields.txt
@@ -805,10 +805,13 @@ For each field, we describe the default widget used if you don't specify
     Also takes ``max_length`` and ``min_length``, which work just as they do for
     ``CharField``.
 
-    The optional argument ``error_message`` is also accepted for backwards
-    compatibility. The preferred way to provide an error message is to use the
-    ``error_messages`` argument, passing a dictionary with ``'invalid'`` as a key
-    and the error message as the value.
+    .. deprecated:: 1.8
+
+        The optional argument ``error_message`` is also accepted for backwards
+        compatibility but will be removed in Django 2.0. The preferred way to
+        provide an error message is to use the :attr:`~Field.error_messages`
+        argument, passing a dictionary with ``'invalid'`` as a key and the error
+        message as the value.
 
 ``SlugField``
 ~~~~~~~~~~~~~