I tried building from source but I am getting errors importing
paraview.simple:
from paraview.simple import *
Traceback (most recent call last):
File stdin, line 1, in module
File
Thanks, pvpython works. Are compatibility issues with paraview python
modules and mac system python also present for versions of paraview
compiled from the source code?
Thanks
Colin
Quoting pat marion pat.mar...@kitware.com:
The 'paraview' directory is the module. Python treats
It shouldn't be a problem with a build from source version of
ParaView. In that case when you turn on the python option cmake finds
your system python libs and build/links with them. If they happen to
find the wrong set for some reason you can always change them and
rebuild.
David E DeMarle
The 'paraview' directory is the module. Python treats directories that
contain a __init__.py file as modules. So you want your python path to
contain /Applications/ParaView 3.10.1.app/Contents/Python, and drop the
/paraview ending.
But, I recommend you use pvpython instead of python. The
Yes I am experiencing the same trouble with my system python but
pypython works very nicely
Thanks
Colin
Quoting pat marion pat.mar...@kitware.com:
The 'paraview' directory is the module. Python treats directories that
contain a __init__.py file as modules. So you want your python path to
Hello all,
As I understand it, to take advantage of python scripting the
PYTHONPATH variable must be set manually. I have added:
PYTHONPATH=/Applications/ParaView
3.10.1.app/Contents/Python/paraview:${PYTHONPATH}
export PYTHONPATH
Which is the location of .py modules. I am not able to
Hi Colin,
I am not sure about the configuration in Mac OS X, but in Linux I can
access to the paraview python interface from the system wide python
with the following setting of PYTHONPATH:
/opt/Paraview-3.10.1/bin/Utilities/VTKPythonWrapping/site-packages:/opt/Paraview-3.10.1/bin/bin
hope it
