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 pitrou
Recipients pitrou, vinay.sajip
Date 2014-08-14.15:17:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1408029480.31.0.129647427763.issue22195@psf.upfronthosting.co.za>
In-reply-to
Content
Often an application (or e.g. a library's test suite), in its early development, will start making print() calls, and later will want to switch to the logging module. However the logging module doesn't offer any facility for this: you can't print() to a logger object, and loggers don't have a method that reflects print()'s signature.

(note print() only uses the .write() and .flush() methods on its stream argument, so a simple wrapper may make the trick)
History
Date User Action Args
2014-08-14 15:18:00pitrousetrecipients: + pitrou, vinay.sajip
2014-08-14 15:18:00pitrousetmessageid: <1408029480.31.0.129647427763.issue22195@psf.upfronthosting.co.za>
2014-08-14 15:18:00pitroulinkissue22195 messages
2014-08-14 15:17:59pitroucreate