Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork34k
gh-143874: Fix pdb expression output leaking to debuggee stdoutpython/cpython#143881
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
gh-143874: Fix pdb expression output leaking to debuggee stdoutpython/cpython#143881
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Most changes to Pythonrequire a NEWS entry. Add one using theblurb_it web app or theblurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the |
python-cla-botbot commentedJan 15, 2026 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
johnslavik commentedJan 20, 2026
Thank you for your time and effort preparing the patch. This time, we've already merged a fix to this issue --#143875 -- I'll close this for you. |
Uh oh!
There was an error while loading.Please reload this page.
Fixes issue#143874
Problem
In remote or dual-terminal debugging setups, expressions evaluated at the pdb
prompt printed their results to the debuggee's stdout instead of the debugger
output stream.
Cause
In remote pdb mode, expression results were printed directly using
print(),bypassing pdb’s output redirection mechanism.
Fix
Route expression output through
self.message()so results are sent through theappropriate pdb output stream, including the socket-based remote debugger.
Tests
Added regression tests to ensure expression evaluation output is correctly routed
in remote pdb sessions.