From 54848a96dd4a196e81f3d71c61caf84ea8b49f4e Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Sat, 12 Sep 2015 16:27:30 -0400 Subject: Removed versionadded/changed annotations for 1.8. --- docs/topics/forms/index.txt | 4 ---- docs/topics/forms/modelforms.txt | 12 ------------ 2 files changed, 16 deletions(-) (limited to 'docs/topics/forms') diff --git a/docs/topics/forms/index.txt b/docs/topics/forms/index.txt index c9cce5121f..27a5314347 100644 --- a/docs/topics/forms/index.txt +++ b/docs/topics/forms/index.txt @@ -615,10 +615,6 @@ errors. For example, ``{{ form.non_field_errors }}`` would look like:
  • Generic validation error
    • -.. versionchanged:: 1.8 - - The ``nonfield`` class as described in the example above was added. - See :doc:`/ref/forms/api` for more on errors, styling, and working with form attributes in templates. diff --git a/docs/topics/forms/modelforms.txt b/docs/topics/forms/modelforms.txt index e9898c6fff..6370636d4e 100644 --- a/docs/topics/forms/modelforms.txt +++ b/docs/topics/forms/modelforms.txt @@ -436,12 +436,6 @@ In addition, Django applies the following rule: if you set ``editable=False`` on the model field, *any* form created from the model via ``ModelForm`` will not include that field. -.. versionchanged:: 1.8 - - In older versions, omitting both ``fields`` and ``exclude`` resulted in - a form with all the model's fields. Doing this now raises an - :exc:`~django.core.exceptions.ImproperlyConfigured` exception. - .. note:: Any fields not included in a form by the above logic @@ -745,12 +739,6 @@ exclude:: >>> AuthorFormSet = modelformset_factory(Author, exclude=('birth_date',)) -.. versionchanged:: 1.8 - - In older versions, omitting both ``fields`` and ``exclude`` resulted in - a formset with all the model's fields. Doing this now raises an - :exc:`~django.core.exceptions.ImproperlyConfigured` exception. - This will create a formset that is capable of working with the data associated with the ``Author`` model. It works just like a regular formset:: -- cgit v1.3