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

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

Mus — Thu, 10 Jun 2021 15:06:03 GMT

Thanks Ian!

I was having the exact same issue on a MacOS Big Sur. Running the SEGGER app from the terminal solved the issue.

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

Carl Richard — Thu, 11 Feb 2021 15:32:41 GMT

Thanks for the advice! Forwarding it.

Best regards,
Carl Richard

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

rlb — Thu, 11 Feb 2021 15:28:27 GMT

Your developers / QA should test NCS install procedure with Apple Xcode already installed.. I believe that was part of my problem with multiple Python / Python3 executables. And perhaps add a diagnostic / troubleshooting script to verify tools are installed and accessible where they are expected by NCS.

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

Carl Richard — Thu, 11 Feb 2021 15:18:26 GMT

Thanks for your details on this issue guys! We're still working hard on getting making the installation procedure for NCS on macOS more straightforward. I'm reporting the information you here to the developers.

IanAber, apologies for a delayed reply here. As the issue is marked "answered" I don't get continued updates on activity. Just wanted to add as well that I agree that IDE is usually the way to go for most developers, but personally I find it much more efficient to work in a more general editor, like VS Code, and build on the command line.

Best regards,
Carl Richard

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

doozMen — Thu, 11 Feb 2021 11:20:01 GMT

So I resulted to you earliar answer and lauched from commandline. Now it is working! Thanks a lot. This took me 3 days but now looking forward to connect things!

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

doozMen — Thu, 11 Feb 2021 11:17:07 GMT

I installed using the toolchain manager and it keeps using the version that got installed with the toolchain manager as I see in the output `File "/opt/nordic/ncs/v1.4.2/toolchain/Cellar/python@3.8/3.8.2/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/west/manifest.py"`

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

doozMen — Thu, 11 Feb 2021 11:06:00 GMT

python 3.8.2. I will update Python then ...

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

IanAber — Wed, 10 Feb 2021 14:47:00 GMT

If you open a terminal window and type python3 --version what version does it report? For a successful install of the Nordic tools this appears to need to be Python 3.9.0 or higher.

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

doozMen — Wed, 10 Feb 2021 08:22:29 GMT

Sorry but I did both and I keep having this issue. I'm switching to windows now but would be grate if this could be fixed. :)

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

IanAber — Fri, 11 Dec 2020 15:21:20 GMT

I ran into another issue that was not resolved by editing the python.cmake. I was unable to change the project configuration because it was also using the wrong version of Python. I did a little more digging.

The fundamental problem here is that if you execute Segger Embedded Studio from spotlight or finder it does NOT use the path environment variable defined for whatever shell you use in Terminal. OS X Catalina on the Mac now uses zsh so when using terminal you get the path as defined in ~/.zprofile. OS X comes with an installation of Python in the /usr/bin folder but this is actually Python3.8 whereas following the instructions in the Nordic getting started guide results in a home brew installation of Python3.9. Python3.9 is found first on the path when executing from a zsh shell but when executing from a finder or spotlight launched GUI app the first location on the path is /usr/bin and this results in Python3.8 being found by the find_package command in cmake.

There appear to be two ways to solve this problem.

1. If you do not want ot mess with the path settings for all GUI applications you can simply launch Segger Embedded Studio from a terminal shell. e.g. Open Terminal and enter (including the double quotes) "/Applications/arm_segger_embedded_studio_v520b_macos_x64_nordic/SEGGER Embedded Studio for ARM 5.20b.app/Contents/MacOS/emStudio"

2. You can set the GUI path by executing this command from a terminal session.
sudo launchctl config user path /usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin.
This will place the home brew managed executables ahead of the built in path and cause GUI launched applications to pick up the correct version of Python. You will need to reboot to get this to take effect.

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

IanAber — Tue, 24 Nov 2020 14:27:25 GMT

I understand. I find it odd that anyone would seriously want to use the command line to build a project when there is a perfectly good ide.

The problem you have with OS X is that it ships with python and you cannot override it easily. Since Seeger has a specific setting to provide the python interpreter it seems odd that this would then be ignored later. Why provide the setting?

I would set up a definition for the python executable in the shell environment and document that as a requirement for command line compilation. Anyone using command line stuff will be very happy to add that to their shell environment.

Another option is simply don’t set the python path in the make file if it is already set. You could even spit out a debug line to say you found an existing value and did not override it.

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

Carl Richard — Tue, 24 Nov 2020 10:01:04 GMT

Hi, Ian! Thanks for suggesting this fix. However, note that this will block the user from building on the command line as it leads to erroneous behavior in the west.cmake script. I believe this stems from the command line environment not having PYTHON_EXECUTABLE defined, while SES does have it defined. I believe the best way to mitigate this issue is to ensure that the correct python distribution is used when installing and handling packages.

We're working hard on providing adequate support for MacOS and Linux so we're thankful for all input!

Best regards,
Carl Richard

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

IanAber — Sun, 22 Nov 2020 01:42:14 GMT

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.

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

crasspm — Fri, 23 Oct 2020 18:18:09 GMT

Ya, I again had to revert to master after trying the 1.3.1 release...

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

rlb — Thu, 22 Oct 2020 12:49:44 GMT

Same! Crazy this still has not been resolved in release branch.

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

24thFrame — Sat, 20 Jun 2020 00:38:45 GMT

I was also having this issue and using master in the "Toolchain Manager" worked for me. Would be great to know when a stable version is available that has this fix.

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

crasspm — Fri, 19 Jun 2020 22:07:02 GMT

Thanks Jan Erik, using master has worked for me as well.

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

Jan Erik — Fri, 19 Jun 2020 08:26:12 GMT

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.

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

Jan Erik — Fri, 19 Jun 2020 08:13:15 GMT

I might have accidentally written the opposite of what I did.

For http_application_update sample I'm using the NS version, because the LTE modem doesn't support secure mode.

For blinky I'm using the safe version.

All of this is working fine in version 1.3.0-rc1.

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

crasspm — Fri, 19 Jun 2020 05:03:02 GMT

The best I can tell even if I load the NS board I'm still building the SPM, where the error occurs. You can see in Jan Erik's post that the log says "Changed board to secure nrf9160dk_nrf9160 (NOT NS)"

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

crasspm — Thu, 18 Jun 2020 21:43:03 GMT

Same!