PyBlosxom status: 03/28/2009

Note: This is an old post in a blog with a lot of posts over a long span of time. The world has changed, technologies have changed, and I've changed. It's likely this is out of date, the code doesn't work, the ideas haven't aged well, or the ideas were terrible to begin with. Let me know if you think this is something that needs updating.

It's been a long time since the last status. PyBlosxom 2.0 had been stagnating for a year and I decided to move it out of the way, put it out of its misery, and start new progress with the PyBlosxom 1.4.3 tag. I scaled back the vision and now I'm working on PyBlosxom 1.5.

I've pulled in some of the changes that were destined for 2.0 and added some new ones:

  • lots of code cleanup

  • pyblosxom-cmd script that automates a whole bunch of things and gives plugins command-line abilities

  • re-working the documentation using Sphinx

  • doubling the number of unit tests

  • fixing a lot of bugs

In the very near future, I plan to overhaul the website and fix project infrastructure issues.

That's where things are. Hoping to have an April release of PyBlosxom 1.5.

Want to comment? Send an email to willkg at bluesock dot org. Include the url for the blog entry in your comment so I have some context as to what you're talking about.