R. David Murray added the comment:
Indeed. The whole point of that section is to explain how the library can
refrain from spewing unwanted logging *if the application doesn't care about
logging*. If the application does care (has configured logging), it would be
wrong to block the logging.
Chris Jerdonek added the comment:
> This documentation states that libraries can turn off logging by adding a
> NullHandler:
I don't think that's what the documentation says. It says, "If for some reason
you don’t want these messages printed *in the absence of any logging
configuration* [my
New submission from Aaron Sherman:
This documentation states that libraries can turn off logging by adding a
NullHandler:
http://docs.python.org/2/howto/logging.html#configuring-logging-for-a-library
This is not entirely true. It only holds true if the application which calls
the library has
