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 cool-RR
Recipients cool-RR, vinay.sajip
Date 2016-07-29.20:09:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1469822965.14.0.109412472968.issue27650@psf.upfronthosting.co.za>
In-reply-to
Content
A while ago I was debugging through code that uses the `logging` module, and I was looking at `Logger` objects and possibly other kinds of objects (maybe handlers? It was a while ago.)

I was frustrated because I was trying to figure out what a particular logger was, but typing `logger` in the shell just showed the opaque `<logging.Logger object at 0x0000000002293550>`. I would like to know the name of the logger without bothering to do `logger.name`.

I suggest that we do a run over the `logging` module and see which classes could have a helpful `__repr__` added to them. I might have time to do this, but first I want to know whether there is a general agreement that such a patch would be welcome.
History
Date User Action Args
2016-07-29 20:09:25cool-RRsetrecipients: + cool-RR, vinay.sajip
2016-07-29 20:09:25cool-RRsetmessageid: <1469822965.14.0.109412472968.issue27650@psf.upfronthosting.co.za>
2016-07-29 20:09:25cool-RRlinkissue27650 messages
2016-07-29 20:09:24cool-RRcreate