From 00a84fc6f3bb8cca15113e4d41e710123d182b4a Mon Sep 17 00:00:00 2001 From: Jacob Walls Date: Fri, 5 Sep 2025 13:49:08 -0400 Subject: Removed versionadded/changed annotations for 5.2. --- docs/topics/testing/overview.txt | 5 ----- docs/topics/testing/tools.txt | 5 ----- 2 files changed, 10 deletions(-) (limited to 'docs/topics/testing') diff --git a/docs/topics/testing/overview.txt b/docs/topics/testing/overview.txt index aa171a8caa..8ec1652ba3 100644 --- a/docs/topics/testing/overview.txt +++ b/docs/topics/testing/overview.txt @@ -281,11 +281,6 @@ To prevent serialized data from being loaded twice, setting :data:`~django.db.models.signals.post_migrate` signal when flushing the test database. -.. versionchanged:: 5.2 - - For :class:`TransactionTestCase`, serialized migration data is made - available during ``setUpClass()``. - Other test conditions --------------------- diff --git a/docs/topics/testing/tools.txt b/docs/topics/testing/tools.txt index bd41d6221b..b2b89556bd 100644 --- a/docs/topics/testing/tools.txt +++ b/docs/topics/testing/tools.txt @@ -1254,11 +1254,6 @@ By default, fixtures are only loaded into the ``default`` database. If you are using multiple databases and set :attr:`TransactionTestCase.databases`, fixtures will be loaded into all specified databases. -.. versionchanged:: 5.2 - - For :class:`TransactionTestCase`, fixtures were made available during - ``setUpClass()``. - URLconf configuration --------------------- -- cgit v1.3