Answers for "Configuring Anaconda environment in FME"

Answer by notmyname

notmyname — Tue, 23 Apr 2019 20:03:54 GMT

I had a similar issue configuring Anaconda with FME, this post helped but missed some details on compatibility.Hopefully this saves someone some time in the future

-The version of FME/Anaconda/Python must all be compatible.I have FME 2018.1 and require features implemented in non 2.7 python, while the current version of Anaconda is python 3.7 (No 2018 fme support).So I had to find an old version of Anaconda that supports a version 3 of python supported by FME.Anaconda3-4.2.0-Windows-x86_64 fills this need with python 3.5.Alternatively updating FME to 2019 would also solve this problem.

-Specify the paths per@david_rpost

-If there is a compatibility of python issues FME will revert to it's default installation, ignoring the Anaconda install

-I also don't have local admin but the non-admin local install of Anaconda seems to work just fine (AppData\Local\Continuum\

Answer by david_r

david_r — Wed, 05 Dec 2018 09:55:03 GMT

I was able to use FME with Anaconda as the Python interpreter using the following setup:

FME 2018.1, 64-bit version
Anaconda 4.5.11 with Python 3.6, 64-bit version

In FME Options:

In the workspace scripting parameters:

I think the most important aspect is to match up the "bitness" of FME and Anaconda, you cannot use FME 32-bit and Anaconda 64-bit, for example.

Answer by david_r

david_r — Wed, 05 Dec 2018 08:25:06 GMT

The path to the dll isn't necessarily what will determine which Python interpreter is actually used.Have you tried setting the PYTHONHOME environment variable?In more recent versions of FME 2018.1 you can set PYTHONHOME in the FME options, in earlier versions you'll have to define it as a system environment variable (and possibly restart your PC for it to take effect).