diff options
| author | Aymeric Augustin <aymeric.augustin@m4x.org> | 2012-06-07 15:02:35 +0200 |
|---|---|---|
| committer | Aymeric Augustin <aymeric.augustin@m4x.org> | 2012-06-07 15:02:35 +0200 |
| commit | c28e700c7e54e3071f173b34a12eb1c4f6e39552 (patch) | |
| tree | 7b82ef60a2ca6a9d5d28cd10d3bea40f1b791284 /docs/ref/forms | |
| parent | 6492e8e5e6643c5a90d71727af7f17a362b9362b (diff) | |
Removed references to changes made in 1.2.
Thanks Florian Apolloner for the patch.
Diffstat (limited to 'docs/ref/forms')
| -rw-r--r-- | docs/ref/forms/api.txt | 4 | ||||
| -rw-r--r-- | docs/ref/forms/fields.txt | 14 | ||||
| -rw-r--r-- | docs/ref/forms/validation.txt | 3 |
3 files changed, 0 insertions, 21 deletions
diff --git a/docs/ref/forms/api.txt b/docs/ref/forms/api.txt index a866fc550c..50488b026a 100644 --- a/docs/ref/forms/api.txt +++ b/docs/ref/forms/api.txt @@ -377,8 +377,6 @@ a form object, and each rendering method returns a Unicode object. Styling required or erroneous form rows ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -.. versionadded:: 1.2 - It's pretty common to style form rows and fields that are required or have errors. For example, you might want to present required form rows in bold and highlight errors in red. @@ -638,8 +636,6 @@ For a field's list of errors, access the field's ``errors`` attribute. .. method:: BoundField.css_classes() - .. versionadded:: 1.2 - When you use Django's rendering shortcuts, CSS classes are used to indicate required form fields or fields that contain errors. If you're manually rendering a form, you can access these CSS classes using the diff --git a/docs/ref/forms/fields.txt b/docs/ref/forms/fields.txt index 6e7d85f586..d9bfbc5e45 100644 --- a/docs/ref/forms/fields.txt +++ b/docs/ref/forms/fields.txt @@ -256,8 +256,6 @@ error message keys it uses. ``validators`` ~~~~~~~~~~~~~~ -.. versionadded:: 1.2 - .. attribute:: Field.validators The ``validators`` argument lets you provide a list of validation functions @@ -268,8 +266,6 @@ See the :doc:`validators documentation </ref/validators>` for more information. ``localize`` ~~~~~~~~~~~~ -.. versionadded:: 1.2 - .. attribute:: Field.localize The ``localize`` argument enables the localization of form data, input as well @@ -492,11 +488,6 @@ For each field, we describe the default widget used if you don't specify If provided, these arguments ensure that the string is at most or at least the given length. -.. versionchanged:: 1.2 - The EmailField previously did not recognize email addresses as valid that - contained an IDN (Internationalized Domain Name; a domain containing - unicode characters) domain part. This has now been corrected. - ``FileField`` ~~~~~~~~~~~~~ @@ -815,11 +806,6 @@ For each field, we describe the default widget used if you don't specify These are the same as ``CharField.max_length`` and ``CharField.min_length``. -.. versionchanged:: 1.2 - The URLField previously did not recognize URLs as valid that contained an IDN - (Internationalized Domain Name; a domain name containing unicode characters) - domain name. This has now been corrected. - Slightly complex built-in ``Field`` classes ------------------------------------------- diff --git a/docs/ref/forms/validation.txt b/docs/ref/forms/validation.txt index 42006bba90..f1642148b5 100644 --- a/docs/ref/forms/validation.txt +++ b/docs/ref/forms/validation.txt @@ -1,8 +1,6 @@ Form and field validation ========================= -.. versionchanged:: 1.2 - Form validation happens when the data is cleaned. If you want to customize this process, there are various places you can change, each one serving a different purpose. Three types of cleaning methods are run during form @@ -175,7 +173,6 @@ previous features. Using validators ~~~~~~~~~~~~~~~~ -.. versionadded:: 1.2 Django's form (and model) fields support use of simple utility functions and classes known as validators. These can be passed to a field's constructor, via |
