Author nicdumz
Recipients nicdumz
Date 2009-04-27.06:24:00
SpamBayes Score 4.13057e-08
Marked as misclassified No
Message-id <1240813443.12.0.48308121403.issue5851@psf.upfronthosting.co.za>
In-reply-to
Content
Hello!

gc.set_debug is provided to help debugging a leaking program. That tool
can be very useful indeed. 

Debugging information, however, is written to sys.stderr, and there are
cases where this behavior can be a problem: chances are that stderr can
be already used to output other information.

Currently, to debug a verbose program writing to stderr, one has to
either first reduce/suppress the stderr output noise from its program
before activating set_debug, OR has to redirect the whole mixed stderr
output, and filter it afterwards. 

I'd like very much the possibility to configure myself where the gc
debugger will write its output.

My suggestion would be to have set_debug converted from set_debug(flags)
to set_debug(flags, stream=sys.stderr), stream being any valid file
object, but any solution allowing me to customize the output target of
the gc debugger would be welcome.

Thanks!
History
Date User Action Args
2009-04-27 06:24:03nicdumzsetrecipients: + nicdumz
2009-04-27 06:24:03nicdumzsetmessageid: <1240813443.12.0.48308121403.issue5851@psf.upfronthosting.co.za>
2009-04-27 06:24:01nicdumzlinkissue5851 messages
2009-04-27 06:24:00nicdumzcreate