A while ago I wrote WPHP (or perhaps more accurately I put it together from other people's pieces) for embedding a PHP app in a WSGI facade. The ultimate goal of that was actually to run specifically Wordpress under Python. So I spent some time last night doing that, and created PyWordpress. It seems to work. It's really very small, since WPHP does almost all the work. (I might implement the Paste appinstall deployment setup which would expand its scope, but I'm not sure.)

It does open up some development questions. The biggest one is that this requires modifications to the Wordpress source. Right now you just need the source plus a fixed wp-config.php. But if the appinstall stuff is implemented a new wp-admin/install.php will required. Ultimately we want to embed Wordpress in Zope with topp.zwsgi, which means that authentication will come from Zope, so the authentication routines probably will have to change to respect REMOTE_USER. Any number of other things may be added. I doubt these would be reasonable upstream changes, though maybe so (you could implement similar things with appropriate Apache configuration).

So, I have to figure out how to manage a minor fork of the Wordpress code, while also tracking upstream updates. So it looks like I have a real use for Distributed Version Control. I guess there's really just two options I'd consider: bzr (or maybe Mercurial -- it's hard for me to really distinguish them) or svk -- svk seems unremarkable except for its relation to Subversion, but I want to track a Subversion repository, so maybe it's perfect, I dunno.