[Python-checkins] cpython: whatsnew: unittest import time SkipTest reported as skip not error.

Fri Jan 3 19:05:00 CET 2014

http://hg.python.org/cpython/rev/22235c8e0a33
changeset: 88278:22235c8e0a33
user: R David Murray <rdmurray at bitdance.com>
date: Fri Jan 03 13:03:36 2014 -0500
summary:
 whatsnew: unittest import time SkipTest reported as skip not error.
files:
 Doc/library/unittest.rst | 5 +++--
 Doc/whatsnew/3.4.rst | 4 ++++
 2 files changed, 7 insertions(+), 2 deletions(-)

diff --git a/Doc/library/unittest.rst b/Doc/library/unittest.rst
--- a/Doc/library/unittest.rst
+++ b/Doc/library/unittest.rst
@@ -559,8 +559,9 @@
 Usually you can use :meth:`TestCase.skipTest` or one of the skipping
 decorators instead of raising this directly.
 
-Skipped tests will not have :meth:`setUp` or :meth:`tearDown` run around them.
-Skipped classes will not have :meth:`setUpClass` or :meth:`tearDownClass` run.
+Skipped tests will not have :meth:`~TestCase.setUp` or :meth:`~TestCase.tearDown` run around them.
+Skipped classes will not have :meth:`~TestCase.setUpClass` or :meth:`~TestCase.tearDownClass` run.
+Skipped modules will not have :func:`setUpModule` or :func:`tearDownModule` run.
 
 
 .. _subtests:
diff --git a/Doc/whatsnew/3.4.rst b/Doc/whatsnew/3.4.rst
--- a/Doc/whatsnew/3.4.rst
+++ b/Doc/whatsnew/3.4.rst
@@ -1015,6 +1015,10 @@
 *defaultTest*, where previously it only accepted a single test name as a
 string. (Contributed by Jyrki Pulliainen in :issue:`15132`.)
 
+If :class:`~unittest.SkipTest` is raised during test discovery (that is, at the
+module level in the test file), it is now reported as a skip instead of an
+error. (Contributed by Zach Ware in :issue:`16935`.)
+
 
 venv
 ----
-- 
Repository URL: http://hg.python.org/cpython
