Remove vscode-debugger workaround (#264)

closes #262 

The issue where running a single test in the VSCode debugger would
trigger other tests was due to a known bug in pytest ([pytest issue
#7409](pytest-dev/pytest#7409)).

This workaround is no longer necessary because VSCode's Python debugger
([vscode-python-debugger](https://github.com/microsoft/vscode-python-debugger))
depends on [debugpy](https://github.com/microsoft/debugpy), where the
root cause was fixed in [commit
1](microsoft/debugpy@63c0fae#diff-f9ef1bd57538927eef0a8a0a2234e7d8R162)
and [commit
2](microsoft/debugpy@f55bea7),
as referenced in [debugpy issue
#275](microsoft/debugpy#275).

Therefore, the workaround can be safely removed. Simply ensure you're
using the latest version of the VSCode Python Debugger currently
(`2025.8.0`).More info on the extension: [VSCode Python
Debugger](https://marketplace.visualstudio.com/items?itemName=ms-python.debugpy)

Author: ZohebShaikh

.vscode/launch.json

@@ -14,10 +14,6 @@
                 "debug-test"
             ],
             "console": "integratedTerminal",
-            "env": {
-                // Enable break on exception when debugging tests (see: tests/conftest.py)
-                "PYTEST_RAISE": "1",
-            },
         }
     ]
 }

tests/conftest.py

@@ -1,21 +0,0 @@
-import os
-from typing import Any
-
-import pytest
-
-# Prevent pytest from catching exceptions when debugging in vscode so that break on
-# exception works correctly (see: https://github.com/pytest-dev/pytest/issues/7409)
-if os.getenv("PYTEST_RAISE", "0") == "1":
-
-    @pytest.hookimpl(tryfirst=True)
-    def pytest_exception_interact(call: pytest.CallInfo[Any]):
-        if call.excinfo is not None:
-            raise call.excinfo.value
-        else:
-            raise RuntimeError(
-                f"{call} has no exception data, an unknown error has occurred"
-            )
-
-    @pytest.hookimpl(tryfirst=True)
-    def pytest_internalerror(excinfo: pytest.ExceptionInfo[Any]):
-        raise excinfo.value