From b5f0b3478dfcf0335f8ac2038d59f54b4a05f2a0 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Wed, 7 Dec 2016 17:42:31 -0500 Subject: Fixed #27579 -- Added aliases for Python 3's assertion names in SimpleTestCase. --- docs/internals/contributing/writing-code/coding-style.txt | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) (limited to 'docs/internals/contributing/writing-code') diff --git a/docs/internals/contributing/writing-code/coding-style.txt b/docs/internals/contributing/writing-code/coding-style.txt index 7b7712919b..fe0a21c5a5 100644 --- a/docs/internals/contributing/writing-code/coding-style.txt +++ b/docs/internals/contributing/writing-code/coding-style.txt @@ -49,9 +49,8 @@ Python style * In tests, use :meth:`~django.test.SimpleTestCase.assertRaisesMessage` instead of :meth:`~unittest.TestCase.assertRaises` so you can check the exception - message. Use :meth:`~unittest.TestCase.assertRaisesRegex` - (``six.assertRaisesRegex()`` as long as we support Python 2) only if you need - to use regular expression matching. + message. Use :meth:`~unittest.TestCase.assertRaisesRegex` only if you need + regular expression matching. * In test docstrings, state the expected behavior that each test demonstrates. Don't include preambles such as "Tests that" or "Ensures that". -- cgit v1.3