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 vinay.sajip
Recipients BreamoreBoy, Saimadhav.Heblikar, barry, numerodix, pitrou, rhettinger, vinay.sajip
Date 2014-08-17.23:21:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1408317673.4.0.490352316906.issue22195@psf.upfronthosting.co.za>
In-reply-to
Content
Loggers don't deal with output - handlers do - so I would prefer not to add an output-related method to a logger: people confuse the two enough as it is. Note that 

stream = LoggerWriter('foo')

gives an equivalent result to

stream = getLogger('foo').debug_printer()

and in my view the former is preferable.

I agree that there is no compelling reason to replace sys.stdout, though it means that you have to pass file=stream in each print() call.

It also makes more sense to use print() rather than have a separate API that looks just like print(), as you essentially would have to duplicate the functionality of the print() API and track enhancements to it over time (to avoid surprises).
History
Date User Action Args
2014-08-17 23:21:13vinay.sajipsetrecipients: + vinay.sajip, barry, rhettinger, pitrou, BreamoreBoy, numerodix, Saimadhav.Heblikar
2014-08-17 23:21:13vinay.sajipsetmessageid: <1408317673.4.0.490352316906.issue22195@psf.upfronthosting.co.za>
2014-08-17 23:21:13vinay.sajiplinkissue22195 messages
2014-08-17 23:21:13vinay.sajipcreate