The install instructions state to create an environment variable PYTHONPATH that should point to the falco source directory. If you do this then python always runs the code from that source directory, NOT from the installed falco code in the corresponding site-packages directory. In fact the setup.py in falco-python is not needed if you have PYTHONPATH set up correctly. Only pip install -r requirements.txt is needed to run falco. Alternative is to not create PYTHONPATH but then the examples will fail because they can't find the data directory where data files are kept, e.g. influence function files. Creating PYTHONPATH is akin to installing with -e option to pip, i.e. pip install -e .
Install instructions should be updated to clarify this confusion.
The install instructions state to create an environment variable PYTHONPATH that should point to the falco source directory. If you do this then python always runs the code from that source directory, NOT from the installed falco code in the corresponding site-packages directory. In fact the setup.py in falco-python is not needed if you have PYTHONPATH set up correctly. Only pip install -r requirements.txt is needed to run falco. Alternative is to not create PYTHONPATH but then the examples will fail because they can't find the data directory where data files are kept, e.g. influence function files. Creating PYTHONPATH is akin to installing with -e option to pip, i.e. pip install -e .
Install instructions should be updated to clarify this confusion.