pyblosxom progress

, Will Kahn-Greene | share this (mastodon)
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.

There's been a flurry of email on the PyBlosxom mailing lists over the last month. I'm totally buried at the moment, so I haven't had time to go through them and figure out what it all means in the grand scheme of things.

I updated the todo list with everything in my head right now (though I'm sure there's other things floating around that aren't on that page).

Robert Wall is working on doing analysis on PyBlosxom and coming up with some code to fix issues he's uncovering.

Hopefully, his work and the work of others will result in some big fixes to PyBlosxom that will (hopefully) simplify the architecture, reduce the number of performance issues, and open up more possibilities.

I also finished up work on Planet PyBlosxom which I had been threatening to do for a while now.

Lots of progress, though. I wish I had more free time to help grease the skids a bit.

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.