[Numpy-discussion] Corrupted installation?
tom.k.cook at gmail.com
Tue Jul 3 07:59:23 EDT 2018
I have a remote sensing platform that uses Numpy on a raspberry pi. There
are about a dozen of these installed. Three days ago, the Python part of
the software started crashing during startup, with this exception message:
Traceback (most recent call last):
File "/home/azi/board/sensor_logger.py", line 16, in <module>
from board.measurement.data import Expression, MeasurementData
File "/home/azi/board/measurement/data.py", line 2, in <module>
import numpy as np
File "/usr/lib/python3/dist-packages/numpy/__init__.py", line 153, in
from . import add_newdocs
File "/usr/lib/python3/dist-packages/numpy/add_newdocs.py", line 13, in
from numpy.lib import add_newdoc
File "/usr/lib/python3/dist-packages/numpy/lib/__init__.py", line 8, in
from .type_check import *
File "/usr/lib/python3/dist-packages/numpy/lib/type_check.py", line 11,
import numpy.core.numeric as _nx
File "/usr/lib/python3/dist-packages/numpy/core/__init__.py", line 7, in
from . import umath
SystemError: initialization of umath raised unreported exception
I'm running numpy 1.8.2 on python 3.4.2 on a Raspberry Pi running Raspbian
Jessie. I realise these are somewhat old, but as the software is running
in the field (and I mean literally in a field - on another continent) I'm
not in a great position to update them.
Can anyone give me a pointer on how to debug this? As far as I can tell,
umath.cpython-34m-arm-linux-gnueabihf.so has not changed recently. In
fact, as far as I can tell, nothing changed around the time this stopped
working. But I guess something must have!
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion