3cf80d3fcf
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. |
||
|---|---|---|
| .. | ||
| _images | ||
| contributing | ||
| deprecation.txt | ||
| git.txt | ||
| howto-release-django.txt | ||
| index.txt | ||
| mailing-lists.txt | ||
| organization.txt | ||
| release-process.txt | ||
| security.txt | ||