-
Notifications
You must be signed in to change notification settings - Fork 61
Open
Description
This isn't a bug, just something I observed, and I'm wondering if somebody has a way around it.
I'm using mode through Faust.
I want to debug my worker code so I put import pdb; pdb.set_trace() in. The breakpoint gets hit and I can use pdb, but all the output is being filtered through the logging mechanism, so it looks like this:
[2020-05-03 12:46:59,075] [1] [WARNING] (Pdb)
[2020-05-03 12:47:00,147] [1] [WARNING] 59 async for log in logs:
[2020-05-03 12:47:00,147] [1] [WARNING] 60 pdb.set_trace()
[2020-05-03 12:47:00,148] [1] [WARNING] 63 cid = log.MESSAGE.get('CID')
[2020-05-03 12:47:00,148] [1] [WARNING] 64 -> loop = asyncio.get_running_loop()
Is there a way to disable this logging feature? Or is there a different recommended way of debugging?
Steps to reproduce
- Put
import pdb; pdb.set_trace()orbreakpoint()into a worker code. - trigger that code
Versions
- Python version: 3.8.1
- Mode version: 4.3.2
- Operating system: python:3.8.1 Docker image on Linux
Metadata
Metadata
Assignees
Labels
No labels