After upgrading from 1.3.0-rc1 to 1.3.0 I get the error ModuleNotFoundError: No module named 'yaml'

Question

Hi, I'm trying to upgrade nRF Connect SDK from 1.3.0-rc1 to 1.3.0 because I need one of the bugfixes to keep developing. I'm on macOS catalina and I've used the Toolchain Manager. Now I get this annoying and apparently well known error message when opening projects: ModuleNotFoundError: No module named 'yaml' I can go back out and "Open IDE" for version 1.3.0-rc1 in Toolchain Manager and then it works. I have fixed my python executable as described in Bjørn's comment at the bottom of this thread. https://devzone.nordicsemi.com/f/nordic-q-a/62172/thingy91-is-useless-without-working-samples-and-sdk/255301#255301 Best regards, 
 Jan Erik Foss BikeFinder

Jan Erik · Accepted Answer

Going to answer my own question here. I enabled master branch in Toolchain Manager, installed it and opened the project. It worked fine, so this has obviously been fixed already. I would really recommend putting some kind of "Known errors and fixes" list next to each version in the toolchain manager. That would have saved me and my company a day of struggling.

IanAber · Answer

I found that there is a couple of lines at the bottom of python.cmake in the zephyr/cmake folder that cause cmake to search for Python and disregard the directive specified in the nRF Connect application. In my system the python found is 3.8 which is part of the developer command line tools in OS X not version 3.9 which is loaded normally based on the path designation for the shell. Since this is not the python version into which yam was installed it fails. 
 To fix this and allow cmake to use the default version of python 'i simply commented these two lines out. 
 # find_package(Python3 ${PYTHON_MINIMUM_REQUIRED} REQUIRED ${PYTHON_EXACT}) # set(PYTHON_EXECUTABLE ${Python3_EXECUTABLE}) 
 The environment variable, PYTHON_EXECUTABLE, is already set so there is no need to change it. 
 Perhaps this should be changed in the distribution for MAC installation.

After upgrading from 1.3.0-rc1 to 1.3.0 I get the error ModuleNotFoundError: No module named 'yaml'

Top Replies