summaryrefslogtreecommitdiff
path: root/docs/topics/forms/modelforms.txt
diff options
context:
space:
mode:
Diffstat (limited to 'docs/topics/forms/modelforms.txt')
-rw-r--r--docs/topics/forms/modelforms.txt12
1 files changed, 0 insertions, 12 deletions
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::