There is a possibility that your system may have software that scans the new installation and has quarantined some of the files that were installed. That’s one possibility… are you Admin on your system? Check with your IT Team as well.
The other question I have is the ‘installation’ approach for the Python Modules…
Our documentation indicates a different commands to install the modules.
https://docs.safe.com/fme/html/FME-Form-Documentation/FME-Form/Workbench/Installing-Python-Packages.htm
Could you try installing these packages again - and you might need --update flag.
I get a feeling you’ll need to create a case with Safe Support if the above doesn’t help you out.
Hi @steveatsafe,
That is a good tip. We do have a bunch of security software, but there is a way to get the installed modules approved after they trigger a block. Not sure about actual quarantining, but I will ask my IT.
Are you saying that a quarantined (or corrupted) Python module could cause FME not to run a translation at all? Even when no Python is being used in the Workspace?
Yes, you are correct that I am installing the modules not quite like the documentation, but it was the only way I could do it without triggering the security (this was done with admin). I had to do the full path for fme.exe and be inside the ‘python’ folder. But, I have had success installing another module the same way (PyMuPDF) and it has binaries as well. Before installing the spaCy module, I did update my pip, per instructions.
What is strange is that even though I am trying to install the modules into the Program Files\FME folder, the files always end up in my Users\Appdata\Roaming folder.
At any rate, I just tested spaCy with a PythonCreator on my 2023.2 version :
import spacy
nlp = spacy.load("en_core_web_sm")
import en_core_web_sm
nlp = en_core_web_sm.load()
doc = nlp("This is a sentence.")
print(e(w.text, w.pos_) for w in doc])
It worked perfectly. So that means the module is not the issue. I have had problems before where FME would not launch. As I recall, it had to do with one of the ‘Qt***’ files.
I made a case with Safe Support, so we’ll get to the bottom of this either way. Thanks for the info!