Blosxom is nice, but unfortunately it's implemented in a write-only language.
This is a problem, because I already have ideas for pushing it in new
directions but I'm constantly confronted by the Perl Problem.
Luckily, any time something worthwhile is written in Perl, somebody comes
along and rewrites it in Python (and Ruby, and Scheme, and countless other
flavors of various weeks). Thus, we have PyBlosxom. PyBlosxom
is much younger than Blosxom, so it's not surprising that it's a little rougher
around the edges. The documentation is much worse than the already shaky
documentation for Blosxom. Even important plugins that come bundled with
PyBlosxom, like the comments plugin, fail to document basic things like which
variables they provide for use in your flavour files. The PyBlosxom folks would
be well advised to follow the Blosxom example and use an informally standardized
format for documenting plugins. Something along the lines of
- Configuration Parameters and Instructions
- Variables provided
Also, it is repeatedly
stated that PyXML is a dependency for various plugins, which is not true since
the xml module in question has been included in the Python standard library
since Python 2.0. Finally, PyBlosxom is often advertized as being compatible
with Blosxom flavours, but this is not true. PB uses a similar scheme, but the
variables you use within the flavour files are different and there are
differences in the set of files contained in a flavour.
Having said all that, I'm still happy to be switching. It's painful for
me to work with a system that I can't tweak and extend, and I'd like to see how
useful I can make this blog be. With some improvements in the documentation,
PyBlosxom should be a good platform for exploring blog-space.