from .qhull import *
ImportError: dlopen(/Applications/ParaView-5.7.0-936-ga45459775a.app/Contents/Python/scipy/spatial/qhull.so, 2): Symbol not found: _main
Referenced from: /Applications/ParaView-5.7.0-936-ga45459775a.app/Contents/Python/scipy/spatial/qhull.so
Expected in: flat namespace
in /Applications/ParaView-5.7.0-936-ga45459775a.app/Contents/Python/scipy/spatial/qhull.so
```
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [January 6, 2020, 9:30am UTC](https://discourse.paraview.org/t/paraview-5-7-doesnt-work-scipy-internal-python-module/3267/3 "2020-01-06T09:30:40Z")
Are you using our release from [https://www.paraview.org/download/](https://www.paraview.org/download/)
Works fine on linux here.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [January 6, 2020, 9:30am UTC](https://discourse.paraview.org/t/paraview-5-7-doesnt-work-scipy-internal-python-module/3267/4 "2020-01-06T09:30:59Z")
@cory.quammen
---
### Author:  [@MBG](https://discourse.paraview.org/u/MBG)
#### Post date: [January 6, 2020, 10:07am UTC](https://discourse.paraview.org/t/paraview-5-7-doesnt-work-scipy-internal-python-module/3267/5 "2020-01-06T10:07:29Z")
MacOS is not equal to Linux. Try MacOS build by your link.
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [January 6, 2020, 1:48pm UTC](https://discourse.paraview.org/t/paraview-5-7-doesnt-work-scipy-internal-python-module/3267/6 "2020-01-06T13:48:35Z")
I am able to run `from scipy.spatial import cKDTree` with the Kitware binaries of 5.7.0.
---
### Author:  [@MBG](https://discourse.paraview.org/u/MBG)
#### Post date: [January 6, 2020, 2:03pm UTC](https://discourse.paraview.org/t/paraview-5-7-doesnt-work-scipy-internal-python-module/3267/7 "2020-01-06T14:03:43Z")
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [January 6, 2020, 2:51pm UTC](https://discourse.paraview.org/t/paraview-5-7-doesnt-work-scipy-internal-python-module/3267/8 "2020-01-06T14:51:40Z")
What version of macOS are you running? Since 5.7 uses the system Python, that could explain the difference. I am running macOS 10.14.6.
---
### Author:  [@MBG](https://discourse.paraview.org/u/MBG)
#### Post date: [January 6, 2020, 2:56pm UTC](https://discourse.paraview.org/t/paraview-5-7-doesnt-work-scipy-internal-python-module/3267/9 "2020-01-06T14:56:07Z")
MacOS 10.14.6 (18G2022)
ParaView Python Library Path: /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
ParaView Python Library Version: 2.7.16 (default, Oct 16 2019, 00:34:56)
[GCC 4.2.1 Compatible Apple LLVM 10.0.1 (clang-1001.0.37.14)]
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [January 6, 2020, 6:05pm UTC](https://discourse.paraview.org/t/paraview-5-7-doesnt-work-scipy-internal-python-module/3267/10 "2020-01-06T18:05:51Z")
Strange, I have the same Python version and Path on my system.
I don’t know why it is looking for a `main` function in `qhull.so` on your system but not mine.
Can you run
`/Applications/ParaView-5.7.0.app/Contents/MacOS/paraview -dr`
to try running with a default environment and settings?
---
### Author:  [@MBG](https://discourse.paraview.org/u/MBG)
#### Post date: [January 6, 2020, 6:24pm UTC](https://discourse.paraview.org/t/paraview-5-7-doesnt-work-scipy-internal-python-module/3267/11 "2020-01-06T18:24:38Z")
I uninstalled and installed ParaView 5.7 again and the issue is the same and it’s not depends of PYTHONPATH env variable:
unset PYTHONPATH; /Applications/ParaView-5.7.0.app/Contents/MacOS/paraview -dr
```
from scipy.spatial import cKDTree
Traceback (most recent call last):
File "", line 1, in
File "/Applications/ParaView-5.7.0.app/Contents/Python/scipy/spatial/ __init__.py", line 100, in
from .qhull import *
ImportError: dlopen(/Applications/ParaView-5.7.0.app/Contents/Python/scipy/spatial/qhull.so, 2): Symbol not found: _main
Referenced from: /Applications/ParaView-5.7.0.app/Contents/Python/scipy/spatial/qhull.so
Expected in: flat namespace
in /Applications/ParaView-5.7.0.app/Contents/Python/scipy/spatial/qhull.so
```
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [January 6, 2020, 6:38pm UTC](https://discourse.paraview.org/t/paraview-5-7-doesnt-work-scipy-internal-python-module/3267/12 "2020-01-06T18:38:51Z")
Thanks for trying. Thoughts, @ben.boeckel?
---
### Author:  [@MBG](https://discourse.paraview.org/u/MBG)
#### Post date: [January 13, 2020, 5:25pm UTC](https://discourse.paraview.org/t/paraview-5-7-doesnt-work-scipy-internal-python-module/3267/13 "2020-01-13T17:25:24Z")
Maybe the issue is not so important if we will have soon ParaView 5.8 with Python 3:
> [@ParaView w/ Python 3 on Mac - when?](https://discourse.paraview.org/t/paraview-w-python-3-on-mac-when/3083/10):
>
> pvpython is just python with the correct PYTHONPATH and LD\_LIBRARY\_PATH passed in. Using a separate executable spares the user of knowing where the python modules and libraries are in the ParaView install or build hierarchy. There is another more subtle differences because python has all functionality built in while pvpython accesses the python functionality through dynamic libraries but it would work the same most of the time.
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [January 14, 2020, 3:26pm UTC](https://discourse.paraview.org/t/paraview-5-7-doesnt-work-scipy-internal-python-module/3267/14 "2020-01-14T15:26:20Z")
Very strange. I don’t know what would cause it to happen on one machine and not another, sorry. Looking for `main` is very odd (macOS mangling involves putting a leading `_` on symbols).