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 ezio.melotti, michael.foord, pitrou, r.david.murray, vinay.sajip
Date 2013-09-07.00:10:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1378512637.2498.6.camel@fsol>
In-reply-to <>
> So making assertions about logging is very common, but I *always* do
> this by just mocking out the logger and making an assertion about the
> call. It's trivially easy to do.

Only works if you test the exact logger that will be triggered, rather
than e.g. a child in the hierarchy (and the exact logging method, for
that matter, too).
Date User Action Args
2013-09-07 00:10:40pitrousetrecipients: + pitrou, vinay.sajip, ezio.melotti, r.david.murray, michael.foord
2013-09-07 00:10:40pitroulinkissue18937 messages
2013-09-07 00:10:40pitroucreate