[Pyblosxom-devel] pyblosxom logging

[Neil S. <nei...@us...>]

As I mentioned in IRC, as it is, there's nothing really wrong in
pyblosxom's logging--that is, the foundation's pretty much
rock-solid (if you can't tell, I'm a big fan of Python's logging
module).

Most of the problem, as it relates to the bug jordi has been
encountering, lies with plugins.  I've noticed that most plugins
don't do any logging at all: in fact, most don't do any
error-handling *at all*.  Having written a few plugins myself,
I'm also guilty of this.

At the moment, I can't decide between diving into the existing
comments plugin and liberally adding support for logging, and
just getting off of my lazy bum and write my own comments plugin,
one which will easier to understand (for me, anyway).

I've still a few days left to lounge around, before I forced by
circumstances to *really* look for a job.  I'll see what I come
up with.

In any case, if anyone should decide to tackle the existing
comments plugin, you ought to add "properly supporting logging"
to your to-do list.

Welp, it's *really* early (for me, anyway); I should probably get
something to eat first.

Later, guys.  Stay frosty.
-- 
Neil Santos
Disgruntled Paradigms :: Code Monkey  //  Doing software The Right Way(TM)

[HTTP] neil.diosa.ph :: [XMPP] ne...@xm... :: [Y!M] neil_santos18

"Throwing a book of rules at a terrible programmer just creates a terrible
 programmer with a bruise on their head where the book bounced off."
                                                              -- Jeff Atwood

v4sw7LMYRhw5ln7pr5Fck4ma3u7OSLw2Gm3l7OArchi6e0t5Tb8/en7g6aI!sr9p-2/-4 hackerkey.com