HI @johnnygalambos, thanks for the question.
I haven't worked with ArcPro cloned Python environments but I imagine this should be possible to set up as long as the FME Engines know about the Python environment you want to use. At the end of
this documentation page there is a section titled "Changing the Python Interpreter" - following those instructions should add the Python path for your custom interpreter to the FME Engines path. You can check this by printing the system path from a job running on FME Server.
Eg.
import sys
print(sys.path)
You may also append the path to your custom interpreter directly in your script with:
import sys
sys.path.append(<path to python>)
I believe your workspace will need to have the appropriate interpreter set as a workspace parameter as well. A good start might be to try to set up your workspace to run in FME Workbench on your FME Server machine before publishing to FME Server and setting up the FME Engines to use the interpreter.
Hope this helps
Nathan
HI @johnnygalambos, thanks for the question.
I haven't worked with ArcPro cloned Python environments but I imagine this should be possible to set up as long as the FME Engines know about the Python environment you want to use. At the end of
this documentation page there is a section titled "Changing the Python Interpreter" - following those instructions should add the Python path for your custom interpreter to the FME Engines path. You can check this by printing the system path from a job running on FME Server.
Eg.
import sys
print(sys.path)
You may also append the path to your custom interpreter directly in your script with:
import sys
sys.path.append(<path to python>)
I believe your workspace will need to have the appropriate interpreter set as a workspace parameter as well. A good start might be to try to set up your workspace to run in FME Workbench on your FME Server machine before publishing to FME Server and setting up the FME Engines to use the interpreter.
Hope this helps
Nathan
Hi Nathan,
I was skeptical of the custom interpreter steps because I thought they looked more geared more toward non-ArcGIS Pro Python installs and I'm hesitant to override server wide configuration for just a couple of scripts that need the ArcGIS Pro libraries. Will run this past our server admin though. I really like your second sys.path suggestion. Will give that a go and report back. Thanks for your help!
John
