This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gvanrossum
Recipients gvanrossum
Date 2008-01-11.01:05:04
SpamBayes Score 0.031272803
Marked as misclassified No
Message-id <1200013506.35.0.644025895195.issue1786@psf.upfronthosting.co.za>
In-reply-to
Content
When you type a command in pdb that happens to print something, the
output goes to sys.stdout, even if self.stdout references another file.
 This makes it hard to debug code running inside a web server where
sys.stdout/stdout are connected to a socket (or a WSGI wrapper file);
the output "disappears" and ends up messing up the response.

Attached is a fix that temporarily changes sys.stdin/stdout to the
debugger's input and output.  What do people think of this?
History
Date User Action Args
2008-01-11 01:05:06gvanrossumsetspambayes_score: 0.0312728 -> 0.031272803
recipients: + gvanrossum
2008-01-11 01:05:06gvanrossumsetspambayes_score: 0.0312728 -> 0.0312728
messageid: <1200013506.35.0.644025895195.issue1786@psf.upfronthosting.co.za>
2008-01-11 01:05:05gvanrossumlinkissue1786 messages
2008-01-11 01:05:04gvanrossumcreate