mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-08-04 10:59:45 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

Fixed #30573 -- Rephrased documentation to avoid words that minimise the involved difficulty.

Browse source 
This patch does not remove all occurrences of the words in question.
Rather, I went through all of the occurrences of the words listed
below, and judged if they a) suggested the reader had some kind of
knowledge/experience, and b) if they added anything of value (including
tone of voice, etc). I left most of the words alone. I looked at the
following words:

- simply/simple
- easy/easier/easiest
- obvious
- just
- merely
- straightforward
- ridiculous

Thanks to Carlton Gibson for guidance on how to approach this issue, and
to Tim Bell for providing the idea. But the enormous lion's share of
thanks go to Adam Johnson for his patient and helpful review.
This commit is contained in:
Tobias Kunze 2019-06-17 16:54:55 +02:00 • committed by Mariusz Felisiak
parent addabc492b
commit 4a954cfd11
149 changed files with 1101 additions and 1157 deletions
Download patch file Download diff file Expand all files Collapse all files

19
docs/topics/forms/modelforms.txt
View file

@ -389,9 +389,8 @@ you've manually saved the instance produced by the form, you can invoke
>>> f.save_m2m()
Calling ``save_m2m()`` is only required if you use ``save(commit=False)``.
When you use a simple ``save()`` on a form, all data -- including
many-to-many data -- is saved without the need for any additional method calls.
For example:
When you use a ``save()`` on a form, all data -- including many-to-many data --
is saved without the need for any additional method calls. For example:
.. code-block:: python
@ -731,8 +730,8 @@ to make::
>>> from myapp.models import Book
>>> BookForm = modelform_factory(Book, fields=("author", "title"))
This can also be used to make simple modifications to existing forms, for
example by specifying the widgets to be used for a given field::
This can also be used to make modifications to existing forms, for example by
specifying the widgets to be used for a given field::
>>> from django.forms import Textarea
>>> Form = modelform_factory(Book, form=BookForm,
@ -755,8 +754,8 @@ Model formsets
.. class:: models.BaseModelFormSet
Like :doc:`regular formsets </topics/forms/formsets>`, Django provides a couple
of enhanced formset classes that make it easy to work with Django models. Let's
reuse the ``Author`` model from above::
of enhanced formset classes to make working with Django models more
convenient. Let's reuse the ``Author`` model from above::
>>> from django.forms import modelformset_factory
>>> from myapp.models import Author
@ -786,8 +785,8 @@ with the ``Author`` model. It works just like a regular formset::
:func:`~django.forms.models.modelformset_factory` uses
:func:`~django.forms.formsets.formset_factory` to generate formsets. This
means that a model formset is just an extension of a basic formset that
knows how to interact with a particular model.
means that a model formset is an extension of a basic formset that knows
how to interact with a particular model.
Changing the queryset
---------------------
@ -952,7 +951,7 @@ extra forms displayed.
Also, ``extra=0`` doesn't prevent creation of new model instances as you can
:ref:`add additional forms with JavaScript <understanding-the-managementform>`
or just send additional POST data. Formsets `don't yet provide functionality
or send additional POST data. Formsets `don't yet provide functionality
<https://code.djangoproject.com/ticket/26142>`_ for an "edit only" view that
prevents creation of new instances.