You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I am using latest PIP version of PuDB, python 3.8, running on Rasberry PI, Ubuntu 20 (arm 64).
My file has
from pudb.remote import set_trace
set_trace(term_size=None, host='127.0.0.1', port=6899)
Our app uses 3rd party modules that print a bunch of log messages to stdout, and they did not provide a way to disable this.
When I connect to debug with
telnet 127.0.0.1 6899
These messages mess up PuDB's UI on my telnet session.
Is there a way to fix this? ( I do not need see to see those messages during the debug session at all, or may be they can be redirected, some how, to a 'console output' panel window in the debugger ? )
I saw a reference to somewhat similar issue in SO 4 years ago
Hello,
I am using latest PIP version of PuDB, python 3.8, running on Rasberry PI, Ubuntu 20 (arm 64).
My file has
Our app uses 3rd party modules that print a bunch of log messages to stdout, and they did not provide a way to disable this.
When I connect to debug with
telnet 127.0.0.1 6899
These messages mess up PuDB's UI on my telnet session.
Is there a way to fix this? ( I do not need see to see those messages during the debug session at all, or may be they can be redirected, some how, to a 'console output' panel window in the debugger ? )
I saw a reference to somewhat similar issue in SO 4 years ago
https://stackoverflow.com/questions/52974938/redirect-django-runserver-output-in-order-to-debug-with-pudb
However I using remote debugging with telnet
The text was updated successfully, but these errors were encountered: