Skip to main content
Question

Path issues while attempting to load Python module

  • August 22, 2024
  • 5 replies
  • 125 views

jhawks
Contributor
Forum|alt.badge.img+7

Path issues while attempting load Python module. FME Pip installed Pypdf. It got installed to:

 

C:\Users\james.hawks\Documents\FME\Plugins\Python\python39\pypdf

 

But workbench cant see that for unknown reasons. 

 

Python Exception <ModuleNotFoundError>: No module named 'PyPDF'

5 replies

bwn
Evangelist
Forum|alt.badge.img+26
  • Evangelist
  • August 22, 2024

Does not really address the problem/cause,  but a general workaround I’ve use is to copy/paste the PIP package files into the FMW folder.

FME seems to always search the FMW folder first for the called Python module, and so this works for me when mucking around with OS Environment Variables has failed otherwise.


jhawks
Contributor
Forum|alt.badge.img+7
  • Author
  • Contributor
  • August 23, 2024

That’s only if the workbench is published correct? If not where is the FMW folder on Client? 


bwn
Evangelist
Forum|alt.badge.img+26
  • Evangelist
  • August 23, 2024
jhawks wrote:

That’s only if the workbench is published correct? If not where is the FMW folder on Client? 


Are you getting an error from a Workbench translation?  The FME Workspace file (FMW) folder location is output on the Translation Log

 

and in Workbench is part of the Application Window Header
 

 


jhawks
Contributor
Forum|alt.badge.img+7
  • Author
  • Contributor
  • August 23, 2024

Workbench for now, will publish eventually. Placed pypdf in the workspace folder. Still no good. 

 

 


jhawks
Contributor
Forum|alt.badge.img+7
  • Author
  • Contributor
  • August 23, 2024

Wait cases matters! Matched it, onto the next error!

 

Python Exception <NameError>: name 'os' is not defined
Error executing string `
import PyPDF


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings