Yes, it works. And now it also works without the full path. The system
path was still set to an earlier version of ParaView (3.14.1).
Thanks for the hint!
Ian
Am 28.05.2014 20:14, schrieb Utkarsh Ayachit:
Try running pvpython by specifying the full path to the executable.
Does that work?
Utkarsh
On Wed, May 28, 2014 at 9:29 AM, Ian Krukow <i.kru...@tu-braunschweig.de> wrote:
Hi all,
I am just starting to use the Python Calculator, but I get an error whenever
I call UpdatePipeline. I use ParaView 4.1.0 32-bit binaries on Windows 7
with the built-in pvpython.
The Calculator works fine with the GUI, and also with the Python Shell (no
error there), but not with a pvpython script like this example:
from paraview.simple import *
sphere = Sphere()
pycalc = PythonCalculator()
pycalc.Expression = 'inputs[0].PointData["Normals"]'
pycalc.UpdatePipeline()
On execution of the last command, I get:
Traceback (most recent call last):
File "<string>", line 1, in <module>
ImportError: No module named paraview
If I go into debug mode with pdb, I can execute UpdatePipeline a second
time, and I do NOT get an error (only one error the first time).
Can somebody tell me, what is wrong?
Kind regards
Ian
_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView
Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview
_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView
Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview
