diff options
| author | David Smith <smithdc@gmail.com> | 2025-05-27 17:37:22 +0100 |
|---|---|---|
| committer | nessita <124304+nessita@users.noreply.github.com> | 2025-08-25 10:51:10 -0300 |
| commit | 6f8e23d1c10c7ce32cea82b65ad2af640015f147 (patch) | |
| tree | 692a42d2a3c54a6610b17cc14679734973d98d89 /docs/howto | |
| parent | ef2f16bc4824ca2b10b7f2845baf4d313c9c0da1 (diff) | |
Refs #36485 -- Removed unnecessary parentheses in :meth: and :func: roles in docs.
Diffstat (limited to 'docs/howto')
| -rw-r--r-- | docs/howto/custom-file-storage.txt | 2 | ||||
| -rw-r--r-- | docs/howto/custom-template-tags.txt | 2 | ||||
| -rw-r--r-- | docs/howto/writing-migrations.txt | 4 |
3 files changed, 4 insertions, 4 deletions
diff --git a/docs/howto/custom-file-storage.txt b/docs/howto/custom-file-storage.txt index 4c9d164a0a..3f9f732e0b 100644 --- a/docs/howto/custom-file-storage.txt +++ b/docs/howto/custom-file-storage.txt @@ -29,7 +29,7 @@ You'll need to follow these steps: option = settings.CUSTOM_STORAGE_OPTIONS ... -#. Your storage class must implement the :meth:`_open()` and :meth:`_save()` +#. Your storage class must implement the :meth:`_open` and :meth:`_save` methods, along with any other methods appropriate to your storage class. See below for more on these methods. diff --git a/docs/howto/custom-template-tags.txt b/docs/howto/custom-template-tags.txt index e56ef54f02..4038bb5184 100644 --- a/docs/howto/custom-template-tags.txt +++ b/docs/howto/custom-template-tags.txt @@ -509,7 +509,7 @@ Simple block tags When a section of rendered template needs to be passed into a custom tag, Django provides the ``simple_block_tag`` helper function to accomplish this. -Similar to :meth:`~django.template.Library.simple_tag()`, this function accepts +Similar to :meth:`~django.template.Library.simple_tag`, this function accepts a custom tag function, but with the additional ``content`` argument, which contains the rendered content as defined inside the tag. This allows dynamic template sections to be easily incorporated into custom tags. diff --git a/docs/howto/writing-migrations.txt b/docs/howto/writing-migrations.txt index 2c52eccbad..dee42ac14e 100644 --- a/docs/howto/writing-migrations.txt +++ b/docs/howto/writing-migrations.txt @@ -37,7 +37,7 @@ attribute:: migrations.RunPython(forwards), ] -You can also provide hints that will be passed to the :meth:`allow_migrate()` +You can also provide hints that will be passed to the :meth:`allow_migrate` method of database routers as ``**hints``: .. code-block:: python @@ -197,7 +197,7 @@ a transaction by setting the ``atomic`` attribute to ``False``:: Within such a migration, all operations are run without a transaction. It's possible to execute parts of the migration inside a transaction using -:func:`~django.db.transaction.atomic()` or by passing ``atomic=True`` to +:func:`~django.db.transaction.atomic` or by passing ``atomic=True`` to ``RunPython``. Here's an example of a non-atomic data migration that updates a large table in |