This has probably been mentioned before, but I think it would be nice if the PythonCaller does some simple syntax checking (indents, variable names, typos etc.). It's always annoying to find out there was an unnecessary error in my code which caused the translation to fail and now I have to copy-paste my (sometimes long) code to an IDE and back again...
[I remember that in the past, you could write all your code in an external *.py file and refer to the classes and functions in the PythonCaller. If this could be reintroduced, that would also be helpful!]
Hi
You can still write your code in an external module, something like
import my_module def FeatureProcessor(feature): my_module.performFunction(feature)
David
1 person upvoted this
+7There's always this possibility, yes, thanks! However, this module then needs to reside in the Python libs folder, doesn't it?
1 person upvoted this
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
1 person upvoted this
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,
import my_moduleand 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.
from my_module import myFunctionEven 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.
import sys sys.path.append(r'C:\\my_python_modules')from my_module import myFunction
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 :-)
1 person upvoted this
+7Thanks @takashi! Considering the circumstances, I think I prefer the sys.path.append() method, so I'll go with that.
1 person upvoted this
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.
1 person upvoted this
+17- Contributor
This is covered by the idea to include and IDE.
1 person upvoted this
+7Agreed, 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.
1 person upvoted this
+15- Safer
Updated idea statusOpen→Archived
Idea merged into:All the votes from this idea have been transferred.
1 person upvoted this
Reply
Helpful Members This Week
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.