As python modules get written, I'll try to keep adding them to this page. And of course, if you have any issues running any of this code, feel free to drop me a line. All of my code, unless otherwise specified is released under the MIT License. Finally, I'm pretty good at pydoc-ing my code, run any module through pydoc, and you'll have nicely formatted documents.

Projects

dbglue - I'm now taking the opportunity to officially rename my pydb project dbglue. dbglue is almost four years old now, predating sqlobject. dbglue is a database objectification framework written in python. The idea is to provide a database agnostic framework, reducing the need to create sql code. In fact, with dbglue used properly, you might never write sql again. The latest version integrates with pycrypto, allowing for encrypted database objects.

pwigen - This is the start of my framework for handling wikis, from a locally editable format. RestructuredText files are converted to html, keeping the original folder layout. When a WikiWord is used as a filename, and that word is found within a file, pwigen will create a link between them. pwigen is in early alpha.

pixt - In pursuing another project, I needed a search engine written in python, something I never really came across. In getting towards my goal, I realized that the next best thing would be a single format, and the ability to search it. Text was the obvious winner, which is why I wrote pixt, a text conversion package.

Discontinued

ckxml - In 2004, I needed a reasonably lightweight xml objectifier object, something that let me write as little code as possible. ckxml is a small library for turning an xml file into an object, really a series of objects. It makes handling xml somewhat simpler in many cases, specifically when wanting to deal with tags as lists. It should be pretty self explanatory to a python xml user.

zem - If you're a fan of Douglas Adams, then you ought know who zem, and zem are. In the spirit of those mattresses, I've created zem, a dynamic UI generator for python. zem uses QT to generate its user interface. An interface (including signals and slots) is described in xml, or a series of xml files. These xml files describe widgets and their usage. The basic goal of zem is to reduce time spent writing code for UIs, rather writing and parsing the zem xml saves development time. I hit version 0.3 before moving on to another project, so zem is unsupported. However, you're more than welcome to try emailing me.