-
Notifications
You must be signed in to change notification settings - Fork 225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2024.1 display clobbered with internal pudb [DEBUG] messages. #649
Comments
That's a fair point. We should probably call PRs implementing this would be welcome. |
Or just add |
I mean, we really need to keep pudb's log level separate from that of the application, despite both of them running with the same Python runtime. |
Huh, I just realized I am talking about warnings, while you are talking about logging. The two are distinct, and both need handling. |
#650 handles the warning end of this. |
Sure. #650 was never going to help with logging, only warnings, sorry. PRs still welcome. |
Okay, this is caused by the Kivy framework that I use attaching to a root logger by default [1] thus also capturing pudb logger that also seems to attach to the root logger. Quck fix is to use [1] https://github.com/kivy/kivy/blob/4a8caf561c37944a21bc004bf8faae2d8237e8a1/kivy/logger.py#L78 |
Ran into this while debugging a Flask app on linux. Would it be possible to ignore the logger.basicConfig settings to prevent this from happening? |
The approach I would prefer would be to swap out the logging configuration for one that logs to pudb's built-in console while the UI is active, similar to #650. Not at the top of my list, but PRs definitely still welcome. |
The problem is using root logger by both pudb and your application (Python uses object references not copies). In my case (Kivy) it was possible to change application behavior not to capture and dump everything from the root logger (see description above). That solved clobbered display for me. I guess Flask can be configured in a similar way but I have no experience with Flask sorry. I guess the best solution would be setting up some sort of internal logger (handler) dedicated for pudb and use its output only in built-in console. |
Describe the bug
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Screenshots
Additional context
Versions
The text was updated successfully, but these errors were encountered: