It might be something in the system config, but it's not obvious. The trouble is, aside from pyMPI, it's a professionally maintained Ubuntu system, with no customization other than package selection. It's a 64-bit machine with a 32-bit Ubuntu installation.
This seems to be related, perhaps, to the problem discussed at http://mail.python.org/pipermail/python-list/2007-March/432606.html The idea is that when built as 64-bit, python doesn't have Py_InitModule4, but rather has Py_InitModule4_64. So the problem seems to be some kind of 32/64 bit issue. The computers that exhibit this problem are all 64-bit processors with a 32-bit installation of Ubuntu. There was a suggestion that " Maybe numpy is more accurate in testing wether it run's on 64 or on 32 bit than the python build script itself and therefore expect's Py_InitModule4 to be present." It also seems to have some smlilarities to https://launchpad.net/ubuntu/+source/clearsilver/+bug/86685 . -- Crash with pyMPI that doesn't happen with latest upstream https://bugs.launchpad.net/bugs/307901 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
