You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OS Microsoft Windows 10 Pro 64bit version 10.0.19045 Build 19045
Python version 3.12.4
OSC tools from 28. Juni 2024
Description
After the Python update to version 3.12, I also updated the KartaView upload scripts. However, the creation of the virtual environment failed. Error message: ModuleNotFoundError: No module named ‘encodings’.
Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding
Python runtime state: core initialized
ModuleNotFoundError: No module named 'encodings'
I have now tested it:
The same problem occurs with the previous version of the upload-scripts, which did not cause me any problems with Python version 3.9.5. I am very unsure where the problem is located.
My System
OS Microsoft Windows 10 Pro 64bit version 10.0.19045 Build 19045
Python version 3.12.4
OSC tools from 28. Juni 2024
Description
After the Python update to version 3.12, I also updated the KartaView upload scripts. However, the creation of the virtual environment failed. Error message: ModuleNotFoundError: No module named ‘encodings’.
Steps to Reproduce
The last line results in:
Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding
Python runtime state: core initialized
ModuleNotFoundError: No module named 'encodings'
See also log file KVI01_Log01.txt
Workaround:
The error disappears if the environment variable PYTHONHOME is set explicitly
The installation then runs without errors. However, no images can be uploaded, the same error occurs here too. See log file
KVI01_Log02.txt .
Explicitly setting PYTHONHOME can also fix the ModuleNotFound error here, but images still cannot be uploaded. However, this is a different issue.
I don't understand why I have to set PYTHONHOME explicitly now, my previously used version of the tools (from 17 January 2023) worked without it.
The text was updated successfully, but these errors were encountered: