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

[awneil]

So what steps do we need to take to have these two different Python versions both installed & usable at the same time on the same machine?

The 'Installing the toolchain' page says that tools have to be in the PATH - but, surely, it is going to matter what order they appear in the PATH ?

[awneil]

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 ?

[Bjørn Kvaale]

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.

[awneil]

Bjørn Kvaale said:

Do you believe that the documentation is a bit vague?

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.

[Bjørn Kvaale]

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. 

[awneil]

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?

[Bjørn Kvaale]

awneil said:

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

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

awneil said:

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

 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.

[awneil]

Bjørn Kvaale said:

All of the python commands are entered in the terminal window by the user (or by a script that you can write yourself)

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

[Bjørn Kvaale]

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