# Incompatible numpy and scipy versions in pvpyton

**URL:** https://discourse.paraview.org/t/incompatible-numpy-and-scipy-versions-in-pvpyton/16548
**Category:** Development
**Tags:** python
**Created:** [April 29, 2025, 9:41am UTC](https://discourse.paraview.org/t/incompatible-numpy-and-scipy-versions-in-pvpyton/16548 "2025-04-29T09:41:21Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![Jnsn](https://discourse.paraview.org/user_avatar/discourse.paraview.org/jnsn/32/10523_2.png) [@Jnsn](https://discourse.paraview.org/u/Jnsn)
#### Post date: [April 29, 2025, 9:41am UTC](https://discourse.paraview.org/t/incompatible-numpy-and-scipy-versions-in-pvpyton/16548/1 "2025-04-29T09:41:22Z")

</div>

Hi ParaView Team,

when using ParaView-5.13.3-osmesa-MPI-Linux-Python3.10-x86\_64/bin/pvpython  
and importing  
from scipy.spatial.transform import Rotation as R

I get follwing ValueError:  
numpy.dtype size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject

It seems scipy is not compatible with `Numpy >= 2`

Best regards,  
Jan

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [April 29, 2025, 9:47am UTC](https://discourse.paraview.org/t/incompatible-numpy-and-scipy-versions-in-pvpyton/16548/2 "2025-04-29T09:47:13Z")

</div>

`from scipy.spatial.transform import Rotation as R`

This import works fine in ParaView nightly binary release on Linux.  
Can you try it: [https://www.paraview.org/download/?version=nightly](https://www.paraview.org/download/?version=nightly)

---

<div class="post-metadata">

### Author: ![Jnsn](https://discourse.paraview.org/user_avatar/discourse.paraview.org/jnsn/32/10523_2.png) [@Jnsn](https://discourse.paraview.org/u/Jnsn)
#### Post date: [April 29, 2025, 10:16am UTC](https://discourse.paraview.org/t/incompatible-numpy-and-scipy-versions-in-pvpyton/16548/3 "2025-04-29T10:16:00Z")

</div>

Just tested, I confirm it works with the Full suite  
ParaView-5.13.20250429-MPI-Linux-Python3.12-x86\_64/bin/pvpython

however unfortunately not with the headless version  
ParaView-5.13.3-2-g22fe491f25-osmesa-MPI-Linux-Python3.10-x86\_64/bin/pvpython

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [April 29, 2025, 10:17am UTC](https://discourse.paraview.org/t/incompatible-numpy-and-scipy-versions-in-pvpyton/16548/4 "2025-04-29T10:17:29Z")

</div>

> [@Jnsn](#):
>
> ParaView-5.13.3-2-g22fe491f25-osmesa-MPI-Linux-Python3.10-x86\_64/bin/pvpython

This is the headless version of the release branch.

There is no headless version anymore for the master branch nor for the upcoming ParaView 6.0

In any case, that means this issue has been fixed.

---

<div class="post-metadata">

### Author: ![Jnsn](https://discourse.paraview.org/user_avatar/discourse.paraview.org/jnsn/32/10523_2.png) [@Jnsn](https://discourse.paraview.org/u/Jnsn)
#### Post date: [April 29, 2025, 10:27am UTC](https://discourse.paraview.org/t/incompatible-numpy-and-scipy-versions-in-pvpyton/16548/5 "2025-04-29T10:27:19Z")

</div>

ok, thanks for clarifying. Besides, I get another error related to the OpenFOAMReader:

```auto
from paraview.simple import *
foam=OpenFOAMReader(FileName='tmp.foam')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/.../ParaView-5.13.20250429-MPI-Linux-Python3.12-x86_64/lib/python3.12/site-packages/paraview/simple/session.py", line 34, in CreateObject
    from paraview.catalyst.detail import IsInsituInput, CreateProducer
  File "/home/.../ParaView-5.13.20250429-MPI-Linux-Python3.12-x86_64/lib/python3.12/site-packages/paraview/catalyst/detail.py", line 7, in <module>
    from ..modules.vtkPVInSitu import vtkInSituPipelinePython
ImportError: /home/.../ParaView-5.13.20250429-MPI-Linux-Python3.12-x86_64/lib/python3.12/site-packages/paraview/modules/../../../../libvtkPVInSitu-pv5.13.so.1: undefined symbol: PyCatalystConduit_Node_Wrap

```

Or shall I open anther task for this?

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [April 29, 2025, 12:07pm UTC](https://discourse.paraview.org/t/incompatible-numpy-and-scipy-versions-in-pvpyton/16548/6 "2025-04-29T12:07:39Z")

</div>

Im unable to reproduce, it works fine with my OpenFOAM data.

---

<div class="post-metadata">

### Author: ![Jnsn](https://discourse.paraview.org/user_avatar/discourse.paraview.org/jnsn/32/10523_2.png) [@Jnsn](https://discourse.paraview.org/u/Jnsn)
#### Post date: [April 29, 2025, 12:23pm UTC](https://discourse.paraview.org/t/incompatible-numpy-and-scipy-versions-in-pvpyton/16548/7 "2025-04-29T12:23:56Z")

</div>

I am getting this only with the nightly binary. I cannot even start the GUI with that version. Starting paraview result in:

```auto
ParaView-5.13.20250429-MPI-Linux-Python3.12-x86_64/bin/paraview-real: symbol lookup error: /usr/lib/x86_64-linux-gnu/libQt6DBus.so.6: undefined symbol: _ZN9QtPrivate23CompatPropertySafePointC1EP14QBindingStatusP20QUntypedPropertyData, version Qt_6

```

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [April 29, 2025, 12:25pm UTC](https://discourse.paraview.org/t/incompatible-numpy-and-scipy-versions-in-pvpyton/16548/8 "2025-04-29T12:25:23Z")

</div>

> [@Jnsn](#):
>
> `/usr/lib/x86_64-linux-gnu/libQt6DBus.so.6`

You should clean your env variables, right now you are using your system Qt because LD\_LIBRARY\_PATH is set.

---

<div class="post-metadata">

### Author: ![Jnsn](https://discourse.paraview.org/user_avatar/discourse.paraview.org/jnsn/32/10523_2.png) [@Jnsn](https://discourse.paraview.org/u/Jnsn)
#### Post date: [April 30, 2025, 8:05am UTC](https://discourse.paraview.org/t/incompatible-numpy-and-scipy-versions-in-pvpyton/16548/9 "2025-04-30T08:05:37Z")

</div>

you are right, after cleaning the environment the nightly binary runs fine, both GUI and pvpython. Thanks for your support!
