Comment 1 for bug 354205

Whoops, just realized this may have been fixed yesterday (perhaps moments before I tested)

Also it should clarify that I don't know what version of Python the package build against, all I mean to indicate is that the location of installation was wrong. It would be interesting if it did actually compile against the python25 headers (and boost compiled against 2.5 headers) since it still seemed to work when I simply put it on my PYTHONPATH.