Slicer Stable 4.11.20210226 issue with scipy package in Linux

There is a problem with scipy package in linux in the new Slicer stable:

from scipy import signal
  File "/home/alex/Programas/Slicer3D/lib/Python/lib/python3.6/site-packages/scipy/signal/__init__.py", line 289, in <module>
    from . import sigtools, windows
  File "/home/alex/Programas/Slicer3D/lib/Python/lib/python3.6/site-packages/scipy/signal/windows/__init__.py", line 41, in <module>
    from .windows import *
  File "/home/alex/Programas/Slicer3D/lib/Python/lib/python3.6/site-packages/scipy/signal/windows/windows.py", line 7, in <module>
    from scipy import linalg, special, fft as sp_fft
  File "/home/alex/Programas/Slicer3D/lib/Python/lib/python3.6/site-packages/scipy/linalg/__init__.py", line 194, in <module>
    from .misc import *
  File "/home/alex/Programas/Slicer3D/lib/Python/lib/python3.6/site-packages/scipy/linalg/misc.py", line 3, in <module>
    from .blas import get_blas_funcs
  File "/home/alex/Programas/Slicer3D/lib/Python/lib/python3.6/site-packages/scipy/linalg/blas.py", line 213, in <module>
    from scipy.linalg import _fblas
ImportError: /home/alex/Programas/Slicer3D/lib/Python/lib/python3.6/site-packages/scipy/linalg/_fblas.cpython-36m-x86_64-linux-gnu.so: ELF load command address/offset not properly aligned

Reinstalling scipy from python console solves the issue

from slicer.util import pip_install
pip_install('scipy -U')

This is an issue we are working on addressing: Importing the numpy C-extensions failed. [slicer 4.11.20200930, archlinux] · Issue #5474 · Slicer/Slicer · GitHub

It affects a number of python packages that are bundled with Slicer. See Slicer-4.11.20200930: Can't import pip-installed Pillow on Linux

Hey, Are there any news on solving this issue? I have several users complaining on this

As noted in the GitHub issue linked above, a fix has been pushed to Slicer as of March. Are you still having the same issue with newer packages?

Sorry, the issue is present in the latest stable version. So the question shall be rewritten as: when a new stable version will contain the solution to this issue?

Sure, we should be putting out another stable snapshot in the next few weeks, most likely after the switch to the new extension manager.

1 Like