Skip to content

Commit e31f3e9

Browse files
colinodellionelmc
authored andcommitted
Add sample error a user might encounter
1 parent 4870f99 commit e31f3e9

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

docs/debuggers.rst

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,13 @@ Debuggers and PyCharm
77
When it comes to TDD one obviously would like to debug tests. Debuggers in Python use mostly the sys.settrace function
88
to gain access to context. Coverage uses the same technique to get access to the lines executed. Coverage does not play
99
well with other tracers simultaneously running. This manifests itself in behaviour that PyCharm might not hit a
10-
breakpoint no matter what the user does. Since it is common practice to have coverage configuration in the pytest.ini
10+
breakpoint no matter what the user does, or encountering an error like this::
11+
12+
PYDEV DEBUGGER WARNING:
13+
sys.settrace() should not be used when the debugger is being used.
14+
This may cause the debugger to stop working correctly.
15+
16+
Since it is common practice to have coverage configuration in the pytest.ini
1117
file and pytest does not support removeopts or similar the `--no-cov` flag can disable coverage completely.
1218

1319
At the reporting part a warning message will show on screen::

0 commit comments

Comments
 (0)