Re: [Paraview] Help with ProgrammableFilter and PATH problem in 5.4.1

2018-03-07 Thread Martin Weinberg
An easy fix is adding: export PYTHONUSERBASE=/dev/null to my bash script that sets the LD_LIBRARY_PATH and PYTHONPATH and "wraps" the paraview invocation.   I also tried setting PYTHONNOUSERSITE but that did not help. Thanks, Shawn for the discussion and may this help someone else down the line.

Re: [Paraview] Help with ProgrammableFilter and PATH problem in 5.4.1

2018-03-07 Thread Martin Weinberg
Okay . . . I figured out the problem but not the fix. The problem is: I installed some packages with pip, and python is prepending ~/.local/lib/python2.7/site-packages paths to PYTHONPATH even when I rewrite the that path in the shell. So if I temporarily rename ~/.local/lib/python2.7/site-packag

Re: [Paraview] Help with ProgrammableFilter and PATH problem in 5.4.1

2018-03-07 Thread Shawn Waldon
The only dependent package I can think of for python filters is numpy, which is used in the dataset adapter code (VTK arrays are wrapped to be numpy array-like). But that should be installed with the binaries and you should get a failed import if it is missing. Shawn On Wed, Mar 7, 2018 at 8:57

Re: [Paraview] Help with ProgrammableFilter and PATH problem in 5.4.1

2018-03-07 Thread Shawn Waldon
Hi Martin, My first guess would be that your state file is trying to load data that isn't there. Then when you run your programmable filter inputs[0] is None and you get this error message. I can't think of anything else that could be going wrong with that script, especially since it works on on