Merge pull request #5004 from blueyed/doc-pdb
doc: fix note about output capturing with pdb
This commit is contained in:
		
						commit
						69a55d334a
					
				|  | @ -384,10 +384,8 @@ in your code and pytest automatically disables its output capture for that test: | ||||||
| * Output capture in other tests is not affected. | * Output capture in other tests is not affected. | ||||||
| * Any prior test output that has already been captured and will be processed as | * Any prior test output that has already been captured and will be processed as | ||||||
|   such. |   such. | ||||||
| * Any later output produced within the same test will not be captured and will | * Output capture gets resumed when ending the debugger session (via the | ||||||
|   instead get sent directly to ``sys.stdout``. Note that this holds true even |   ``continue`` command). | ||||||
|   for test output occurring after you exit the interactive PDB_ tracing session |  | ||||||
|   and continue with the regular test run. |  | ||||||
| 
 | 
 | ||||||
| 
 | 
 | ||||||
| .. _`breakpoint-builtin`: | .. _`breakpoint-builtin`: | ||||||
|  |  | ||||||
		Loading…
	
		Reference in New Issue