nRF5 SDK for Mesh v2.2.0 - Python 2.7 and 3 Coexistence

RE: nRF5 SDK for Mesh v2.2.0 - Python 2.7 and 3 Coexistence

Bjørn Kvaale — Thu, 25 Oct 2018 12:56:16 GMT

Great! Thanks for that! I will update the internal feedback & hopefully the documentation will be updated soon! 🙂

RE: nRF5 SDK for Mesh v2.2.0 - Python 2.7 and 3 Coexistence

awneil — Thu, 25 Oct 2018 12:55:22 GMT

[quote userid="25682" url="~/f/nordic-q-a/39747/nrf5-sdk-for-mesh-v2-2-0---python-2-7-and-3-coexistence/154507"]All of the python commands are entered in the terminal window by the user (or by a script that you can write yourself)[/quote]

Ah - that's the key information that's missing, then!

RE: nRF5 SDK for Mesh v2.2.0 - Python 2.7 and 3 Coexistence

Bjørn Kvaale — Thu, 25 Oct 2018 12:45:03 GMT

[quote user="awneil"]So are you saying that the Mesh SDK assumes that 'python' will start Python 3 ?[/quote]

Yes, as of now I believe that is the case.

[quote user="awneil"]Therefore, I should modify my existing Python 2.7 so that it will not be found by an unqualified 'python' command?[/quote]

You could do this. All of the python commands are entered in the terminal window by the user (or by a script that you can write yourself). What I have done is run a python3 command (like I mentioned in my first comment) every time the documentation says to use python.

RE: nRF5 SDK for Mesh v2.2.0 - Python 2.7 and 3 Coexistence

awneil — Thu, 25 Oct 2018 10:58:55 GMT

So are you saying that the Mesh SDK assumes that 'python' will start Python 3 ?

Therefore, I should modify my existing Python 2.7 so that it will not be found by an unqualified 'python' command?

RE: nRF5 SDK for Mesh v2.2.0 - Python 2.7 and 3 Coexistence

Bjørn Kvaale — Thu, 25 Oct 2018 10:50:55 GMT

I will mention this internally. Thanks for the feedback. Unless you are using the DFU feature, you will not need to use Python 2.7 at all in the mesh sdk. Ideally, all of the mesh tools would use the same version of Python for simplicity.

RE: nRF5 SDK for Mesh v2.2.0 - Python 2.7 and 3 Coexistence

awneil — Thu, 25 Oct 2018 09:52:15 GMT

[quote userid="25682" url="~/f/nordic-q-a/39747/nrf5-sdk-for-mesh-v2-2-0---python-2-7-and-3-coexistence/154381"]Do you believe that the documentation is a bit vague?[/quote]

Vague? It is completely silent!

It needs to clearly state what needs to be done so that the Mesh SDK will correctly find the appropriate version for each of the tools requiring the different versions.

RE: nRF5 SDK for Mesh v2.2.0 - Python 2.7 and 3 Coexistence

Bjørn Kvaale — Thu, 25 Oct 2018 07:09:17 GMT

The points that tesc & I made were supposed to be specific, as well as general points. This is what we have done & that has worked very well so far when supporting the nRF5 SDK for Mesh & developing our own examples/demos. Do you believe that the documentation is a bit vague? Is there anything you would change? Please let us know if anything is still unclear.

RE: nRF5 SDK for Mesh v2.2.0 - Python 2.7 and 3 Coexistence

awneil — Wed, 24 Oct 2018 08:07:07 GMT

Thanks Bjørn Kvaale and tesc, but I understand these general points.

The question is, specifically, how does this need to be set up for the nRF5 SDK for Mesh ?

RE: nRF5 SDK for Mesh v2.2.0 - Python 2.7 and 3 Coexistence

tesc — Wed, 24 Oct 2018 08:03:16 GMT

Hi,

Newer versions of Python 3.x will install as "py" in addition to "python". You may have to rearrange your PATH in order for "python" to refer to the Python 2 install (having the Python 2 directory come first in PATH), but if you install Python 2 before Python 3 then this should work out of the box.

Similarly, by default you can use "pip3" for the Python 3 version of pip, and "pip" for the Python 2 version.

Regards,
Terje

RE: nRF5 SDK for Mesh v2.2.0 - Python 2.7 and 3 Coexistence

Bjørn Kvaale — Wed, 24 Oct 2018 06:21:26 GMT

I agree that this is an issue. Of course, you could always switch which location is first in the path to switch between Python 2 & 3, but this is a time-consuming & annoying process. What I have done is keep the Python 2 application named python & renamed the Python 3 application python3. That way, I can either call python or python3 & do not need to make any changes in the path. Naturally both applications need to be part of the path. This may not be the best solution, but it works fine for me.