Author archives: Mike

RSS feed of Mike

Buying a printer tomorrow (Brother HL 2070N)


Need to get a printer. Every once in a while there's a document that needs to be printed and running around town to get it output on paper is just annoying. Planning on getting the Brother HL 2070N, which has an ethernet interface and reasonable (from reports) Linux drivers. It's nothing special, basically just a ...

Continue reading

I suppose I will have to install Windows (Blech.)


With Python 2.5 out, probably need to build a binary of PyOpenGL-SWIG. That requires re-installing Windows (both machines are corrupt), then getting the whole MS-Toolkit compiler-chain re-built (double blech). Windows is a serious PITA.

The worst part is that I'm actually contributing to the monopoly-value of Windows (network effects) when I support libraries on it, ...

Continue reading

At some point you just have to accept it (Changing core assumptions at the last moment doesn't work...)


I've spent about two solid work-days this week (one un-billable) attempting to find a way to refactor the VoIP project to eliminate some glaring structural problems related to the original spec that keep getting in the way of forward coding. Problem is, they are with core objects that affect pretty much every line of code ...

Continue reading

Hey buddy, looking for an Open Source Python job? (And other miscellany from PyGTA)


Had a good turnout at PyGTA last night. Aaron presented Panometric's (currently proprietary, may get open-sourced) web-application wiki. In essence this is a mechanism that allows users to edit an application's templates using a customised version of docutils that includes a number of directives for including e.g. auto-generated tables and the like. It works by ...

Continue reading

Mail server disappears again (Grr...)


Once again my machine at home has disappeared. So no email today. I actually set up the PII-450 with dovecot yesterday, I was thinking of moving the mail services over to it with an rdiff-backup to the main machine, but didn't get that done yesterday. Sigh.

Ctypes arrays as storage format (Seems natural given the implementation...)


Today (and yesterday) I added support for making ctypes arrays first-class array-storage formats for OpenGL-ctypes. That is, you can do this:
import OpenGL
OpenGL.preferredArray( 'ctypesarrays' )

Before you import OpenGL functions in your application and array-producing calls will then use ctypes arrays for the produced arrays (i.e. glGet* will return ctypes arrays instead of Numpy ...

Continue reading

Adding a type for documentation in epydoc (ctypes "Functions" as routine data-types...)


As mentioned a few posts ago, I've been looking at how to make the OpenGL-ctypes auto-generated documentation useful. What I want to do is to register the ctypes "functions" as regular routines, with docstrings and preferably with structured meta-data such as the data-types of arguments, error-checker and the like displayed in a consistent way.

The ...

Continue reading