Comment 3 for bug 1159817

I'm currently going on the assumption that we simply got a corrupted binary out of the armhf buildd. I'm doing a local rebuild to confirm and if that's the case, will simply push a no-change rebuild.

This assumption is based on the fact that the same python module works on other architectures and that the binding only got very slightly changed between ~alpha3 (working on armhf) and ~rc1 (not working on armhf) with those changes limited to the Container object and not to the import functions.