Opinion on pyblosxom

FYI, Here's an email which I replied to that's in the blosxom mailing
list, with the best of my knowledge on pyblosxom (at least I think so).
Names are cleared to protect the innocent.

----------------------
>  Clearly, it'd be nice to not have a fork for each scripting language,
>  but I'm happy to see a PyBlosxom.

Thank you.

>  I am concerned about it lagging behind, since Python isn't as popular
>  as Perl, and since it's a one-off.

Pyblosxom is not a one-off. Anyway, one of the reasons why you may think
that pyblosxom is lagging behind (like all the other Java, Ruby, and PHP
derivatives) is that we all have a different focus. The reason why I
started with pyblosxom is because I wanted Wiki formatting using blosxom
style weblog entries.

Right now, all of us are a different animal with different focus and
theme.

 * Pyblosxom is the first to have plugins (compared with blosxom and
   some others except PHosxom),
 * the first to come out with text formatting options,
 * the first to come out with a different date scheme,
 * the first to come out with flavour overrides based on the directory
   you are in,
 * the first to allow different types of files to render,
 * the first to have caching of entry,
 * the first to allow user defined metadata in entries,
 * and the first with XMLRPC services. I don't think that's lagging
   behind really. I'd rather think of it as innovation :)

And we've got a team of developers playing around with the code, and if
things work out fine, we will be the first to integrate comments into
pyblosxom (as compared to the external blosxom style) and the first to
allow you to use a different rendering engine like CheetahTemplates
compared to the blosxom one.

>  To me, Blosxom will lead the way, and PyBlosxom will lag. Still, my
>  pro-Python prejudice is keeping me from deciding on Blosxom.

Like I said, different focus. If only there are more python programmers,
I'm sure pyblosxom could do quite well.

>  Failing reassurances that PyBlosxom is keeping good time with
>  Blosxom, can anyone offer a Dive Into Perl (;>) or "Perl To Python
>  Dictionary"?

I can never be 100% back to back blosxom feature compatible. Really,
that means I'll forever be playing catching up and breaking all the nice
things that pyblosxom could become. 



-------------------------------------------------------
This SF.net email is sponsored by: Does your code think in ink? 
You could win a Tablet PC. Get a free Tablet PC hat just for playing. 
What are you waiting for?
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en