CODEWITHSUNDEEP
pythonexepyinstallercodec
EcSync
EcSync

Reputation: 860

Fatal Python error: initfsencoding: unable to load the file system codec

I have created a .exe file of a simple script with intentions to run it on a server however I cannot seem to figure out what this fault means or find any answers online. The fault code is as follows:

Fatal Python error: initfsencoding: unable to load the file system codec
ModuleNotFoundError: No module named 'encodings'

Current thread 0x00003c8c (most recent call first):

To get this far I used pyinstaller 

pyinstaller --onefile MyScript.py

When this didn't work I also tried

pyinstaller MyScript.py

I am running on windows 10, python 3.7 within admin command prompt, within a C:\ file directory.

My sys.path is

['', 'C:\Users\user\AppData\Local\Programs\Python\Python37-32\python37.zip', 'C:\Users\user\AppData\Local\Programs\Python\Python37-32\DLLs', 'C:\Users\user\AppData\Local\Programs\Python\Python37-32\lib', 'C:\Users\user\AppData\Local\Programs\Python\Python37-32', 'C:\Users\user\AppData\Roaming\Python\Python37\site-packages', 'C:\Users\user\AppData\Local\Programs\Python\Python37-32\lib\site-packages', 'C:\Users\user\AppData\Local\Programs\Python\Python37-32\lib\site-packages\win32', 'C:\Users\user\AppData\Local\Programs\Python\Python37-32\lib\site-packages\win32\lib', 'C:\Users\user\AppData\Local\Programs\Python\Python37-32\lib\site-packages\Pythonwin']

Any help is appreciated

Upvotes: 19

Views: 75934

Answers (6)

Alex
Alex

Reputation: 374

I had the very same error message as EcSync. Although most people are pointing to the python setup being wrong this was not the case for me - aside from the fact that my system had not changed from one day to the next when I got the error, my environment variables matched the python sys.path

EcSync solved the problem by including a missing module but their answer is downvoted. I have to add my voice to say that this error was also caused by a missing module. The clue is in the error message:

Fatal Python error: initfsencoding: unable to load the file system codec
ModuleNotFoundError: No module named 'encodings'

I simply modified my spec file to include the encodings module and then everything worked. To do this you may need to specify to pyinstaller to use the spec file provided rather than making one from scratch, and you will have to put the path to the missing module in the datas list of Analysis. See here.

Upvotes: 2

Adrian John
Adrian John

Reputation: 75

I just added the following to the system variables:

PYTHONPATH ----------------------------C:\Python37

enter image description here

Upvotes: 1

user2514185
user2514185

Reputation: 1

Use --standalone will build the binary with whole python environment. You don't need a python install in the destination machine to run it.

Upvotes: 0

ThorSummoner
ThorSummoner

Reputation: 18089

this error means that Py_SetPath forced python to use a path which doesn't include python38.zip, add the full pathname to python38.zip to the Py_SetPath, or don't use Py_SetPath and work with python38._pth instead.

#define PY_SSIZE_T_CLEAN
#include <Python.h>


int main(int argc char **argv)
{
        Py_SetPath(L"C:\\path-to\\python-3.8.5-embed-amd64\\python38.zip;C:\\path-to\\python-3.8.5-embed-amd64");
        Py_Initialize();
        // ...
}

Upvotes: 0

EcSync
EcSync

Reputation: 860

So I managed to fix this issue by rebuilding the exe file and dumping all of the site packages from python home to the exe dist folder. Will go through them again to figure out which one was causing issues.

EDIT

I narrowed this down and found the specific issue was the plotly package was not being dumped into the dist folder. I am not sure why but this is the only package I was using that pyinstaller wouldn't pick up

Upvotes: -2

Vineeth Sai
Vineeth Sai

Reputation: 3447

Looks like this is happening due to some problem in python installation. Are you sure python is configured properly? Did you add it into ENVIRONMENT VARIABLES?

Most likely it is because your PYTHONPATH ,i.e the one that locates the site-packages is improperly configured. It should work fine once you point PYTHONPATH to the corrent python3.x installation.

Once launch python from your cmd and check which site-packages it is loading.

import sys
sys.path

And then verify what is actually present in your PYTHONHOME

Upvotes: 11

Related Questions