Hi,
I am using the nRF Connect SDK 2.3.0 and running into an issue when calling python from the terminal opened from the Toolchain Manager (via the Open Terminal option).
Calling `python` from this terminal gives me the following error:
Python path configuration: PYTHONHOME = '/home/guilherme/ncs/toolchains/v2.3.0/usr/local' PYTHONPATH = '/home/guilherme/ncs/toolchains/v2.3.0/usr/local/lib/python3.8/site-packages' program name = 'python' isolated = 0 environment = 1 user site = 1 import site = 1 sys._base_executable = '/usr/bin/python' sys.base_prefix = '/home/guilherme/ncs/toolchains/v2.3.0/usr/local' sys.base_exec_prefix = '/home/guilherme/ncs/toolchains/v2.3.0/usr/local' sys.platlibdir = 'lib' sys.executable = '/usr/bin/python' sys.prefix = '/home/guilherme/ncs/toolchains/v2.3.0/usr/local' sys.exec_prefix = '/home/guilherme/ncs/toolchains/v2.3.0/usr/local' sys.path = [ '/home/guilherme/ncs/toolchains/v2.3.0/usr/local/lib/python3.8/site-packages', '/home/guilherme/ncs/toolchains/v2.3.0/usr/local/lib/python310.zip', '/home/guilherme/ncs/toolchains/v2.3.0/usr/local/lib/python3.10', '/home/guilherme/ncs/toolchains/v2.3.0/usr/local/lib/python3.10/lib-dynload', ] 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' Current thread 0x00007f6c65212740 (most recent call first): <no Python frame>
If I use python3 instead of python, it works as expected. This causes me more trouble down the line because I have a west extension that uses subprocess.Popen() and I run into the exact same error trace.
What might be causing this and how do I solve the problem?