Users/berk/work/paraview3-build/lib/ Release:/Users/berk/work/paraview3-build/lib/site-packages In those cases add the correct folder where the *.libs reside: Note that depending on your build configuration, your *.libs files may not be under 'lib' but under one of its sub-folders, like 'lib/Release' or 'lib/Debug'. Users/berk/work/paraview3-build/lib:/Users/berk/work/paraview3-build/lib/site-packages This tutorial will be using the python integrated development environment IDLE. You do not have to set PYTHONPATH when using these. You can also use either pvpython (for stand-alone or client/server execution), pvbatch (for non-interactive, distributed batch processing) or the python shell invoked from Tools|Python Shell using the ParaView client to execute Python scripts.

These files are the shared libraries located in the paraview binary directory and python modules in the paraview directory: paraview/simple.py, paraview/vtk.py etc. This module can be loaded from any python interpreter as long as the necessary files are in PYTHONPATH. To start interacting with the Server Manager, you have to load the 'simple' module. You may also visit the Python recipes page for some examples. This document is a short introduction to ParaView's Python interface. Note: Server Manager is a library that is designed to make it easy to build distributed client-server applications. Using Python, users and developers can gain access to the ParaView engine called Server Manager. This support is available as part of the ParaView client (paraview), an MPI-enabled batch application (pvbatch), the ParaView python client (pvpython), or any other Python-enabled application. ParaView offers rich scripting support through Python. 5.6 Writing Data Files (ParaView 3.9 or later).

Paraview python filters