PDB (pdbpp) disrupted by prefect logs

[teocns]

Bug summary

I use pdbpp for debugging and its meant to provide enhanced debugging experience especially text rendering side.

Somehow prefect disrupts text rendering of the pdb display:

1. Hit n which leads you to the next call in the stack
2. Prefect's logger will flush logs and render text on screen
3. The whole screen is cleared (!!)
4. At this point the debugger screen is completely cleared and only shows an empty prompt

... which results in me having to run PDB's ll command to display code context of where I am (which shouldn't be happening)

---

My follow up question would be if we can disable prefect run logs globally?
As a side thought we can write a hook to interop with pdb and have better timing in flushing and rendering when PDB context is active

[teocns]

cc @zzstoatzz in case my issue gets buried

[zzstoatzz]

hi @teocns - can you give an MRE for this? that will help us understand if there's a non-disruptive change we can make to be compatible with this 3rd party

[teocns]

Ok further investigation and this is actually an issue belonging to pdbpps side, it occurs in many other circumstances whereas logging handlers are overridden which it is very sensitive to changes. Closing, thanks for jumping in @zzstoatzz !

EDIT: PuDB > PDBpp