mirror of
https://github.com/django/django.git
synced 2025-08-04 19:08:28 +00:00
Fixed #31395 -- Made setUpTestData enforce in-memory data isolation.
Since it's introduction in Django 1.8 setUpTestData has been suffering from a documented but confusing caveat due to its sharing of attributes assigned during its execution with all test instances. By keeping track of class attributes assigned during the setUpTestData phase its possible to ensure only deep copies are provided to test instances on attribute retreival and prevent manual setUp gymnastic to work around the previous lack of in-memory data isolation. Thanks Adam Johnson for the extensive review.
This commit is contained in:
parent
1dd96f731d
commit
3cf80d3fcf
6 changed files with 178 additions and 12 deletions
|
@ -15,6 +15,10 @@ about each item can often be found in the release notes of two versions prior.
|
|||
See the :ref:`Django 3.2 release notes <deprecated-features-3.2>` for more
|
||||
details on these changes.
|
||||
|
||||
* Support for assigning objects which don't support creating deep copies with
|
||||
``copy.deepcopy()`` to class attributes in ``TestCase.setUpTestData()`` will
|
||||
be removed.
|
||||
|
||||
.. _deprecation-removed-in-4.0:
|
||||
|
||||
4.0
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue