how to upgrade python version on Sbrio?

[Milliee]

Hello everyone, I'm working on Sbrio with Python 3.5.5 installation, I need to work with 3.9 version but unfortunately I couldn't finish its installation from source because of the limited space I have, is there any other way to upgrade python version? or maybe if I could find python 3.5.5 path to uninstall it and have enough space to install the version I need ?

[Jay14159265]

I think NI has updated how you do this, check out the link

https://www.ni.com/en-us/support/documentation/supplemental/18/installing-python-for-calling-python-...

You could probably use that info to find the install called by labview, nuke it, then install a new version. 

[rolfk]

What sbRIO board is that on? Has the Python source finally grown to the same amounts as a full featured .Net installation? That would sound like a memory hog.

I see from the official Python source download page that the version 3.9.13  source tarball is about 26 MB. That should easily extract on any recent sbRIO and let you also install the gcc devutils and any other tools like Perl that may be needed during build time, from the NI OPKG repository.

[Milliee]

Thank you for your reply, actually I am using Sbrio9607, it is true that the python installation folder takes about 25 Mb but it takes more when starting the Installation, I found this link https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000YOPDCA4&l=en-TN to customize the software installation on Sbrio and to not install the python Package , but unfortunately it didn't work for me, because of "unresolved dependecies".. Now and after reinstalling the Linux image system 2021 with removing some packages ,I have now 160 Mb and I have successfully installed Python 3.9.2.. now I only have 20 MB as a free space, the problem here that the python 3.5.5 still exist, I didn't know how to uninstall it and keep the 3.9.2 version.. 

[Jay14159265]

Ok, so is Labview still linked to 3.5.5 or now linked to 3.9.2?

If you open python from the command line, which version launches? 

If labview is still linked to 3.5.5 , you can simply have it execute the following: 

import sys

print(sys.executable) 

which will tell you where the 3.5.5 interpreter is installed. 

Just be carefull, I don't know if labview uses the system interpreter or its own, I imagine it uses its own. I don't have my linux machine in front of me or I would check. Don't remove the system interpreter, it may cause other issues, best to leave that alone. 

On a side note, if you are trying to wrangle 20MB of space on your system, you might need to re-think the big picture here.

Might be worth cleaning up some other garbage from your linux install than removing python interpreters. 

[Milliee]

Thank you ! actually the location of the interpreter is /usr/bin/python, it's not a directory so I couldn't delete it.. I was thinking of adding the 3.9 version to PATH, it's not that evident though with the known line command.. so maybe I would just move the scripts located in Bin of 3.9 installation to the path manually with the command (mv) here's a screenshot of the warning I got after finishing the Installation.

I would have customized the software installation with elemintating python, only if I could solve these errors mentioned below, even after checking the solution suggested by NI https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019WjeSAE&l=en-TN  I don't know what's meant by "requires a base system of a certain version".. 

Bests,

[Jay14159265]

---

@Milliee wrote:

 so maybe I would just move the scripts located in Bin of 3.9 installation to the path manually with the command (mv) here's a screenshot of the warning I got after finishing the Installation.

---

That is playing with fire, did you manually put those scripts there in the first place? Before you do anything like that, how are you calling python from labview is it through system exe or through a labview python node? 

---

@Milliee wrote:

Bests,

---

As far as the error goes, what is not to understand? you don't have the correct base systems installed. You need to install them if you want it to work. 

[Milliee]

No, I haven't done this neither now nor before, 

I am calling python through sys exe.

About the errors that have occured, what I don't understand is when I installed Linux 21 image, the versions of all the softwares installed are 21 and 20 as shown in the picture below.

Although when I start the customized installation, the suggested Softwares are with older versions, as you can see in the pictures ( run time-engine 16.0 and Labview Real-Time 15.0 when I have Lbaview RT module with version 21 installed on my host computer..) so I was wondering if it is what's causing the errors..

[Jay14159265]

---

@Milliee wrote:

No, I haven't done this neither now nor before, 

I am calling python through sys exe.

About the errors that have occured, what I don't understand is when I installed Linux 21 image, the versions of all the softwares installed are 21 and 20 as shown in the picture below

Although when I start the customized installation, the suggested Softwares are with older versions, as you can see in the pictures ( run time-engine 16.0 and Labview Real-Time 15.0 when I have Lbaview RT module with version 21 installed on my host computer..) so I was wondering if it is what's causing the errors..

---

As far as calling python, You have much more freedom when using the system exe than a python node so that is good. What I don't know is if labview will bark at you if you remove the interpreter that it is expecting to use, the 3.5.whatever. It might be required for the RTE.

Usually a good way to save space is to not include unused drivers NI is notorious for installing all sorts of junk you don't need unless you configure the install just the way you want , Not sure how much of this you have done but you can free up quite a bit of space. 

For the version issue, it has been a while since I worked on a RT target and it did not work the first time I did a custom install. Maybe someone that is current with the RT wizard can have some input on what the defaults are and why they would give errors.  All I can say is that if the system says it needs something you either need to provide it, or configure the system to not need the dependency.