pip3 install -r nrf/scripts/requirements.txt doesn't install all packages

RE: pip3 install -r nrf/scripts/requirements.txt doesn't install all packages

Karl Ylvisaker — Mon, 18 Jul 2022 05:05:53 GMT

No problem at all, I am happy to help! :)

Best regards,
Karl

RE: pip3 install -r nrf/scripts/requirements.txt doesn't install all packages

snowuyl — Mon, 18 Jul 2022 04:35:41 GMT

Thanks for your suggestions!

RE: pip3 install -r nrf/scripts/requirements.txt doesn't install all packages

Karl Ylvisaker — Mon, 18 Jul 2022 04:24:39 GMT

Hello rory and snowuyl,

Is this causing you any issues when you attempt to build a project later on? Is there any complaint about missing packages or incorrect packet versions?

In general I would recommend that you make use of virtual environments to make sure that you differentiate between the two different toolchains and their requirements.
The easiest and recommended way of doing this is to use the nRF Connect extensions for Visual Studio code, which lets you effortlessly change between the different toolchains, without having to manually run the requirement scripts or west updates in-between each usage.

Changing between different toolchains is as easy as selecting it from this dropdown menu:

When you open a new nRF Terminal (ctrl + shift + p, type 'shell') in VSC it will source the environment for the toolchain chosen in this dropdown menu.

Additionally, you could then download and setup the SDK and toolchains using the Toolchain Manager application from nRF Connect for desktop, which is by far the easiest way to manage your toolchains :)

Best regards,
Karl

RE: pip3 install -r nrf/scripts/requirements.txt doesn't install all packages

snowuyl — Sun, 17 Jul 2022 11:58:30 GMT

Thanks for your reply!

RE: pip3 install -r nrf/scripts/requirements.txt doesn't install all packages

Rory — Sun, 17 Jul 2022 11:55:15 GMT

I see this all the time too, as it is printed in red font at the end of the script output. It hasn't really caused any real pain yet, and I've always thought it had something to do with me switching between NCS 1.5.2 and NCS 2.0.0. When I switch my target NCS version, I always perform a west update and run the three requirements.txt scripts, and I have been seeing this same exact warning lately when I run nrf/scripts/requirements.txt.

I can't tell exactly what's going on, other than a bunch of the packages require a PyYAML version >=6.0, and it looks like previous NCS versions used packages that only required pyyaml 5.4.1, and these versions conflict. I'm not sure if this is really just a warning or what, because it does appear that PyYAML-6.0 gets installed.