|
From: Malthe B. <mb...@gm...> - 2008-03-05 22:10:23
|
Hey Waylan, –– Thanks for your reply. On 05/03/2008, Waylan Limberg <wa...@gm...> wrote: > If your wondering why this is necessary for a command line script like > markdown, remember that many (perhaps most) are using markdown.py > behind a web server which would require the ability to reconfigure > logging. Such a user could conceivably redirect such messages to their > servers error log for review when problems are encountered. In fact, > in most web server configurations this is the only way to debug a > problem. That's a good point, although I would think that at some point, the package reaches a state of maturity where automated tests should take the place of any runtime debugging. That is, ––– if the output is not what's expected, it should be proven in a test such that it can be fixed. I think a good use for log statements is when rare or unexpected events happen, or if the user of the package needs some information. Instead of having the debug statement in the markdown package, I think it should be in the application using markdown, if that application is still in development. \malthe |