Re: [Paraview] Paraview and Python related question

Hi, I think you should *add* the Paraview path to the environment variable. Now you overwrite it. So the typical syntax is (bash): export avar=adir:$avar (Send from my phone, so I hope the formatting is reasonable). Marco Op 23 sep. 2015 01:16 schreef "Amit Goel" : > There

Re: [Paraview] Paraview and Python related question

I have tried setting that too, but it doesnt work. Perhaps its some weird combination of python, tkinter installed using macports with paraview 4.4 pre-built-binary that requires some special trick. I will try on Linux sometimes. Regards amit On Sep 23, 2015, at 12:04 PM, Marco Nawijn

Re: [Paraview] Paraview and Python related question

Thanks for the help. When I set DYLD now the idle stops working: fluid:~ armando$ export DYLD_LIBRARY_PATH=/Applications/ArmandoApps/paraview.app/Contents/Libraries/:$DYLD_LIBRARY_PATH fluid:~ armando$ export

Re: [Paraview] Paraview and Python related question

Hi Amit, Since you appear to be using OSX, the environment variable you want is DYLD_LIBRARY_PATH, not LD_LIBRARY_PATH. HTH, Shawn On Tue, Sep 22, 2015 at 1:32 PM, Amit Goel wrote: > Hi > > I downloaded the Paraview app and put it in a folder. Then I tried > following

[Paraview] Paraview and Python related question

Hi I downloaded the Paraview app and put it in a folder. Then I tried following instructions on this page: http://www.paraview.org/ParaView3/Doc/Nightly/www/py-doc/quick-start.html export PYTHONPATH=/Applications/ArmandoApps/paraview.app/Contents/Python:$PYTHONPATH export

Re: [Paraview] Paraview and Python related question

There is this weird behaviour : fluid:~ armando$ export DYLD_LIBRARY_PATH=/lib fluid:~ armando$ idle idle works just fine even if I point DYLD_LIBRARY_PATH to anything… as in above example /lib But when I set it to paraview: fluid:~ armando$ export