I think the current test case doesn't actually test the remote debug mode. We need add some tests intest_remote_pdb.py:

Let's add some tests like this:

classRemotePdbTestCase(unittest.TestCase):    ...deftest_remote_closure_exec(self):self.pdb._exec_in_closure('(lambda: 123)()', {}, {})outputs=self.sockfile.get_output()messages= [o['message'].strip()foroinoutputsif'message'ino]self.assertIn("123",messages)

I think the current test case doesn't actually test the remote debug mode.

Thank you very much — I couldn’t agree more with your feedback.

Before that, I spent a long time trying to find an appropriate place for the corresponding test case, and still didn’t get it right. <(_ _)>

The issue is real but it's not becauseprint prints tosys.stdout. It's because remote pdb overridesself.message so we have to use that.sys.stdout is actually replaced withself.stdout in local pdb mode.

but it's not because

Totally agree. The actual execution path is:

self.message() →local pdb: print(..., file=self.stdout) → remote pdb: send over the socket

Thank you for helping identify the RCA and clarifying the underlying cause–and–effect relationship.

Thank you for the contribution!

Thanks@hyongtao-code for the PR, and@gaogaotiantian for merging it 🌮🎉.. I'm working now to backport this PR to: 3.14.
🐍🍒⛏🤖

GH-144061 is a backport of this pull request to the3.14 branch.