diff options
| author | Tim Graham <timograham@gmail.com> | 2018-02-08 10:10:28 -0500 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2018-02-08 10:10:47 -0500 |
| commit | 29dd7dcdfdf63e6e2b127273c58f55e81fc7c2e2 (patch) | |
| tree | 52efd77145e95d8130e0ddcac14d48b34359bb62 | |
| parent | 8d03356d35a91e2a8536bae4319f061ccf6c0294 (diff) | |
[2.0.x] Fixed #29107 -- Doc'd that ModelForm doesn't actually inherit from Form.
Backport of ff61a250815d32ff185501a5afef0245fec7d878 from master
| -rw-r--r-- | docs/topics/forms/index.txt | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/docs/topics/forms/index.txt b/docs/topics/forms/index.txt index 86de7d1b06..79bf30a5ab 100644 --- a/docs/topics/forms/index.txt +++ b/docs/topics/forms/index.txt @@ -370,9 +370,11 @@ ready to learn a bit more about the underlying machinery. More about Django :class:`Form` classes ======================================= -All form classes are created as subclasses of :class:`django.forms.Form`, -including the :doc:`ModelForm </topics/forms/modelforms>`, which you encounter -in Django's admin. +All form classes are created as subclasses of either :class:`django.forms.Form` +or :class:`django.forms.ModelForm`. You can think of ``ModelForm`` as a +subclass of ``Form``. ``Form`` and ``ModelForm`` actually inherit common +functionality from a (private) ``BaseForm`` class, but this implementation +detail is rarely important. .. admonition:: Models and Forms |