Merge pull request #13924 from bluetech/lazy-import-unittest

runner: don't treat `unittest.SkipTest` as an interactive exception

Author: bluetech

changelog/13917.bugfix.rst

@@ -0,0 +1 @@
+:class:`unittest.SkipTest` is no longer considered an interactive exception, i.e. :hook:`pytest_exception_interact` is no longer called for it.

src/_pytest/debugging.py

@@ -11,7 +11,6 @@
 import sys
 import types
 from typing import Any
-import unittest
 
 from _pytest import outcomes
 from _pytest._code import ExceptionInfo
@@ -295,9 +294,7 @@ def pytest_exception_interact(
             sys.stdout.write(out)
             sys.stdout.write(err)
         assert call.excinfo is not None
-
-        if not isinstance(call.excinfo.value, unittest.SkipTest):
-            _enter_pdb(node, call.excinfo, report)
+        _enter_pdb(node, call.excinfo, report)
 
     def pytest_internalerror(self, excinfo: ExceptionInfo[BaseException]) -> None:
         exc_or_tb = _postmortem_exc_or_tb(excinfo)

src/_pytest/runner.py

@@ -271,7 +271,10 @@ def check_interactive_exception(call: CallInfo[object], report: BaseReport) -> b
     if hasattr(report, "wasxfail"):
         # Exception was expected.
         return False
-    if isinstance(call.excinfo.value, Skipped | bdb.BdbQuit):
+    unittest = sys.modules.get("unittest")
+    if isinstance(call.excinfo.value, Skipped | bdb.BdbQuit) or (
+        unittest is not None and isinstance(call.excinfo.value, unittest.SkipTest)
+    ):
         # Special control flow exception.
         return False
     return True