summaryrefslogtreecommitdiff
path: root/docs/topics/testing
diff options
context:
space:
mode:
authorMike Edmunds <medmunds@gmail.com>2026-04-17 10:16:37 -0700
committernessita <124304+nessita@users.noreply.github.com>2026-04-24 12:22:34 -0300
commit29eac2648cbc8f4000a391bf6424bc32979b0149 (patch)
tree0634bb488f90ba9732c97f38f078392e22c66c03 /docs/topics/testing
parentd24160ab4855f6971aa1f437720adca6330048a2 (diff)
Replaced references in docs to accepted PEPs with specific Python docs links.
Where the docs used `:pep:` links for established Python language features, replaced them with direct references to the Python docs (usually glossary terms).
Diffstat (limited to 'docs/topics/testing')
-rw-r--r--docs/topics/testing/tools.txt5
1 files changed, 2 insertions, 3 deletions
diff --git a/docs/topics/testing/tools.txt b/docs/topics/testing/tools.txt
index eda1849334..7c238702bf 100644
--- a/docs/topics/testing/tools.txt
+++ b/docs/topics/testing/tools.txt
@@ -1337,7 +1337,7 @@ Overriding settings
For testing purposes it's often useful to change a setting temporarily and
revert to the original value after running the testing code. For this use case
-Django provides a standard Python context manager (see :pep:`343`) called
+Django provides a standard :ref:`context manager <context-managers>` called
:meth:`~django.test.SimpleTestCase.settings`, which can be used like this::
from django.test import TestCase
@@ -1390,8 +1390,7 @@ neither does ``remove`` when the value doesn't exist.
.. function:: override_settings(**kwargs)
In case you want to override a setting for a test method, Django provides the
-:func:`~django.test.override_settings` decorator (see :pep:`318`). It's used
-like this::
+:func:`~django.test.override_settings` :term:`python:decorator`::
from django.test import TestCase, override_settings