Fixed #36005 -- Dropped support for Python 3.10 and 3.11.

1 files changed, 5 insertions, 5 deletions

diff --git a/docs/internals/contributing/writing-code/unit-tests.txt b/docs/internals/contributing/writing-code/unit-tests.txt
index 446d896abe..f4342f69aa 100644
--- a/docs/internals/contributing/writing-code/unit-tests.txt
+++ b/docs/internals/contributing/writing-code/unit-tests.txt
@@ -92,14 +92,14 @@ In addition to the default environments, ``tox`` supports running unit tests
 for other versions of Python and other database backends. Since Django's test
 suite doesn't bundle a settings file for database backends other than SQLite,
 however, you must :ref:`create and provide your own test settings
-<running-unit-tests-settings>`. For example, to run the tests on Python 3.10
+<running-unit-tests-settings>`. For example, to run the tests on Python 3.12
 using PostgreSQL:
 
 .. console::
 
-    $ tox -e py310-postgres -- --settings=my_postgres_settings
+    $ tox -e py312-postgres -- --settings=my_postgres_settings
 
-This command sets up a Python 3.10 virtual environment, installs Django's
+This command sets up a Python 3.12 virtual environment, installs Django's
 test suite dependencies (including those for PostgreSQL), and calls
 ``runtests.py`` with the supplied arguments (in this case,
 ``--settings=my_postgres_settings``).
@@ -114,14 +114,14 @@ above:
 
 .. code-block:: console
 
-    $ DJANGO_SETTINGS_MODULE=my_postgres_settings tox -e py310-postgres
+    $ DJANGO_SETTINGS_MODULE=my_postgres_settings tox -e py312-postgres
 
 Windows users should use:
 
 .. code-block:: doscon
 
     ...\> set DJANGO_SETTINGS_MODULE=my_postgres_settings
-    ...\> tox -e py310-postgres
+    ...\> tox -e py312-postgres
 
 Running the JavaScript tests
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~