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

[Michael B. <mi...@zz...>]

On Oct 6, 2008, at 4:27 PM, Yuri Takhteyev wrote:

>>>
> So, the question is: from the point of view of library users, does it
> make more sense to setup logging levels?  Or should we just leave them
> as undefined?  One potential compromise would be to move all logging
> setup into a function, leaving the library caller an option of calling
> it:
>
>    import markdown
>    markdown.setup_logging()

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.