diff options
| author | Michiel Beijen <mb@x14.nl> | 2017-04-23 22:06:12 +0200 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2017-04-24 20:51:55 -0400 |
| commit | 7eecf496eecdf9ce1227e0ea517d32880e3300d9 (patch) | |
| tree | f213d2fb894edb8c5eeb19ca960547eb84beae1a /docs/topics | |
| parent | 6cbfaba1787b17752361ae4de1fff8d0acfe62f1 (diff) | |
[1.11.x] Renamed "Mac OS X" to "macOS" in docs.
Backport of 5e8625ba643db118a44cb32e9e48bf431ef4da53 from master
Diffstat (limited to 'docs/topics')
| -rw-r--r-- | docs/topics/testing/tools.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/topics/testing/tools.txt b/docs/topics/testing/tools.txt index aadb68d84e..9b2e76cadc 100644 --- a/docs/topics/testing/tools.txt +++ b/docs/topics/testing/tools.txt @@ -723,7 +723,7 @@ If your tests make any database queries, use subclasses ``tearDownClass()`` are run. In the case of :class:`django.test.TestCase`, this will leak the transaction created in ``super()`` which results in various symptoms including a segmentation fault on some platforms (reported - on OS X). If you want to intentionally raise an exception such as + on macOS). If you want to intentionally raise an exception such as :exc:`unittest.SkipTest` in ``setUpClass()``, be sure to do it before calling ``super()`` to avoid this. |