Re: [Python-markdown-discuss] Ticket 18: DEBUG log setting

[Yuri T. <qar...@gm...>]

> the "library" point of view would leave logging levels and handlers
> undefined.  libraries just call logging.getLogger('MARKDOWN').debug("my
> message"), and possibly isEnabledFor() (although that call is known to be
> slow), and the configuration of the "MARKDOWN" logger is left to external
> actors.

Ok. And thanks for your clarification in your previous message, which
for some reason landed in my inbox only after I responded to Waylan's
response to your response.

So: I'll move the logging configuration into main(), define a function
getLogger() as a shorthand for logging.getLogger('MARKDOWN'), and do
logging through it.  We won't configure logging except when getting
called from the command line.  Does this sound like the right plan?

- yuri

-- 
http://sputnik.freewisdom.org/