[seanread]

Hi,

I just installed open foam 3.0 with paraview 4.4 from the source codes on the git repository, and everything is working fine, except that when I try to import a function from a file which is located in the CWD (for example sigan)

ImportError: No module named sigan

I'm using linux mint 17.3, but had the same problem with the debian pack install in ubuntu 15.10 (same version open foam and paraview)

The same problem is not present in my parafoam 4.1 install on another computer (also on linux mint, 17.2), has anyone else had this problem with this on 4.4?

[wyldckat]

Greetings Sean,

This is essentially a Python question The real problem is whether you are trying to import a function or if you are trying to run a script, because the two have different ways of being done.

Loading a Python script as a module requires the folder to be in Python's search path, as defined by the environment variable... er... gotta got look it up... oh, nice, I've written about this in the past: http://www.cfd-online.com/Forums/ope...tml#post571136 post #7 - therefore, you will have to add the current path to the environment variable "PYTHONPATH".

On the other hand, running a Python script from Python... here you go: https://docs.python.org/2/library/fu....html#execfile
So it should be something like this:

execfile("/full/path/to/script/test.py")

Best regards,
Bruno

[seanread]

Thanks Bruno,

I had a similar problem a few months back, and seem to remember I got it working, you can see the post here:

http://www.cfd-online.com/Forums/par...-pvpython.html

The strange thing is that now the same problem is recurring if I try on the original system (linux mint 17.2 with paraview 4.1, as in the above post)

I know for example that if I open python directly (as opposed to pvpython) in the same directory that the same syntax works fine (eg from sigan import *).

I don't remember having to change anything in the python path last time, not sure what I'm doing wrong now...

[wyldckat]

Hi Sean,

ParaView's Python environment is created in a separate environment, which is why the current from where you started ParaView does not match with the one inside the Python environment within ParaView.

I need detailed steps in order to try and replicate the same scenario you are working with. Knowing what the following commands give you in the command line can help:

echo $PYTHONPATH
echo $PV_PLUGIN_PATH

... as well as knowing how exactly you are launching ParaView, namely if from the command line or interactively.

Best regards,
Bruno

[seanread]

Thanks Bruno,

The Python path is /lib/paraview-4.4/site-packages:/lib/paraview-4.4/site-packages/vtk

the PV_PLUGIN_PATH is /home/sean/OpenFOAM/OpenFOAM-4.0.x/platforms/linux64GccDPInt32Opt/lib/paraview-4.4

I'm starting paraview from the terminal, interestingly os.getcwd() is returning the directory from which I started paraview

[wyldckat]

Hi Sean,

Originally Posted by seanread

The Python path is /lib/paraview-4.4/site-packages:/lib/paraview-4.4/site-packages/vtk

That's a somewhat strange path!? How exactly did you install ParaView 4.4?

And what does this command give you?

which paraview

Best regards,
Bruno

[seanread]

which paraview returns

/home/sean/OpenFOAM/ThirdParty-3.0.x/platforms/linux64Gcc/ParaView-4.4.0/bin/paraview


I still haven't set up the python path properly on this install, so the python path is just what is in my old .bashrc (which got copied over in my dejadup backup). PYTHONPATH was defined before the line pointing to $HOME/OpenFOAM/OpenFOAM-3.0.x/etc/bashrc
so it was showing strangely. After fixing this the PYTHONPATH is:

/home/sean/OpenFOAM/ThirdParty-3.0.x/platforms/linux64Gcc/ParaView-4.4.0/lib/paraview-4.4/site-packages:/home/sean/OpenFOAM/ThirdParty-3.0.x/platforms/linux64Gcc/ParaView-4.4.0/lib/paraview-4.4/site-packages/vtk

I installed paraview 4.4 by compiling from the git repository source code (linux mint won't take the debian packages) but was having the same problem on ubuntu 15.10 installed from the debian packages through apt-get

[wyldckat]

Then does it work properly with the updated PYTHONPATH? Or does it still have issues importing the "sigan" file?

[seanread]

No, still the same for sigan or any *.py file

[wyldckat]

Quick answer: "testingMyStuff.py" is my test script:

import os, sys
sys.path.append(os.getcwd())
import testingMyStuff

Source: http://stackoverflow.com/a/1112661

[seanread]

Thanks that worked fine, still not sure why this problem arose in the first place...

[seanread]

Now a quick follow up question, is there a way to add

import os, sys
sys.path.append(os.getcwd())
import testingMyStuff

To pvpython automatically on startup so that I don't have to manually enter it every time I start paraview?

[wyldckat]

Quick answer (although 20 days after your question): It's explained here: http://stackoverflow.com/questions/1...on-interpreter