On Aug 29, 11:02 pm, Thomas Heller [EMAIL PROTECTED] wrote:
BTW: Let me say that the more I useloggingthe more I like it.loggingis a
fantastic package!
Thank you, I can say the same for ctypes and py2exe :-)
Regards,
Vinay Sajip
--
http://mail.python.org/mailman/listinfo/python-list
Vinay Sajip schrieb:
On Aug 27, 11:28 am, Thomas Heller [EMAIL PROTECTED] wrote:
I came up with a workaround that seems to do what I want. I add a NULL
handler
to my top-level logger which is not the root logger but a logger named
'comtypes',
other loggers are named
On Aug 26, 8:05 pm, Thomas Heller [EMAIL PROTECTED] wrote:
I'm using theloggingmodule in my comtypes library to log
'interesting' things that happen. In other words, the idea
is if the user of the library is interested in the details that
happen in the package internally, he (she?) would
Vinay Sajip schrieb:
Suppose a user of logging configures it wrongly by mistake, so that
there are no handlers configured. In this case, if the logging system
were not to output anything at all, then you would have no information
at all about why - leading to a longer time to diagnose the
On Aug 27, 11:28 am, Thomas Heller [EMAIL PROTECTED] wrote:
Vinay Sajip schrieb:
I came up with a workaround that seems to do what I want. I add a NULL
handler
to my top-level logger which is not the root logger but a logger named
'comtypes',
other loggers are named
I'm using the logging module in my comtypes library to log
'interesting' things that happen. In other words, the idea
is if the user of the library is interested in the details that
happen in the package internally, he (she?) would configure
a logging level and handlers that write the log
Thomas Heller [EMAIL PROTECTED] writes:
If the script using the library does NOT configure logging, and
somewhere the library calls logger.error(...) or
logger.critical(...) then he gets a message on stderr saying:
No handlers could be found for logger foo
Right. So, part of the
