diff options
| author | Simon Charette <charette.s@gmail.com> | 2018-11-23 21:22:09 -0500 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2020-05-15 20:22:52 +0200 |
| commit | 3cf80d3fcf7446afdde16a2be515c423f720e54d (patch) | |
| tree | f68aacd6e8f3dab3e250504d16bb1a51ed929bf4 /docs/internals | |
| parent | 1dd96f731df3ca9df0e3ff83a9a8e723dc7e8685 (diff) | |
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.
Diffstat (limited to 'docs/internals')
| -rw-r--r-- | docs/internals/deprecation.txt | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/internals/deprecation.txt b/docs/internals/deprecation.txt index e48356bed1..d4cc1d2d95 100644 --- a/docs/internals/deprecation.txt +++ b/docs/internals/deprecation.txt @@ -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 |