PythonCaller: simple syntax checking

There's always this possibility, yes, thanks! However, this module then needs to reside in the Python libs folder, doesn't it?

You can save the module in the same folder as your workspace too. Either as a .py file parallell to the workspace or in a subfolder as a package.

If you look closely in the FME log, you will see that it automatically adds the workspace folder to the PYTHONPATH when initializing the interpreter.

David

Cool, thanks, good to know! I'll try it out soon! :)

Hi @sander_s, addition to David's comment.

If you have defined a function/class in the external module (e.g. "my_module.py") conforming to the template shown in the "Python Script" parameter, it can be called directly from the script.

In the "Python Script" parameter, just import the module,

and then specify the function/class name qualified by the module name (e.g. "my_module.myFunction") in the "Class or Function to Process Features" parameter.

It's not essential to qualify the name by module name if you use "from - import" to import the function/class.

Even if you have saved the "my_module.py" into an external directory, you can import it by adding the path to the "sys.path" list in the script.

Alternatively, you can also add the directory path to the PYTHONPATH environment variable in the system. If you do so, "sys.path.append..." can be omitted.

Various ways depending on the condition :-)

Thanks @takashi! Considering the circumstances, I think I prefer the sys.path.append() method, so I'll go with that.

I think you can still do this by putting the path to your py folder in an environment variable named PYTHONPATH. Then in your Python Caller start with:

import myModule

Python will find that module on the PYTHONPATH and run it.

Agreed, but I was first ;)

An integrated IDE would definitely be nice to have, but since that would be quite a project on itself, I thought that at least basic syntax checking would make a good first step in that direction.