How to distinguish that the python program is executed on a RPI?

[Elmit]

I am developing Python scripts on different machines, including RPI.

Is there a way to distinguish on which machine I am working, so that I load the right modules?

E.g. PySimpleGUI uses this:

Code: Select all

#!/usr/bin/env python
import sys
if sys.version_info[0] >= 3:
    import PySimpleGUI as sg
else:
    import PySimpleGUI27 as sg

How would I write above to load RPI modules, like camera, GPIO.rpi .... ?

[pfletch101]

I am developing Python scripts on different machines, including RPI.

Is there a way to distinguish on which machine I am working, so that I load the right modules?

E.g. PySimpleGUI uses this:

Code: Select all

#!/usr/bin/env python
import sys
if sys.version_info[0] >= 3:
    import PySimpleGUI as sg
else:
    import PySimpleGUI27 as sg

How would I write above to load RPI modules, like camera, GPIO.rpi .... ?

If I'm not mistaken, the code that you quote is checking whether it is running under Python 2.x or Python 3.x, not determining what hardware it is running on. To do the latter, probably the easiest approach would be to place files in a known location on all your systems with names corresponding to the 'set' of modules that you want to load. Your scripts can then check for the existence of the 'flag' file(s), and load the appropriate modules.

[Andyroo]

You could look at /sys/firmware/devicetree/base/model to see what you are running on but how you would then dynamically select the include modules I have no idea...

[hippy]

I am developing Python scripts on different machines, including RPI.

Is there a way to distinguish on which machine I am working, so that I load the right modules?

There is 'os.name' and I am sure others which can give you information about what the code is being run on. One can search for the presence of various files or check their contents. I personally add a human readable 'device.txt' file in the root directory which specifies what that particular machine is.

Instead of trying to work out what a machine is and what is present one can simply use try-except until you get an import which works -

Code: Select all

try    : import PySimpleGUI   as sg
except : import PySimpleGUI27 as sg

[pfletch101]

I am developing Python scripts on different machines, including RPI.

Is there a way to distinguish on which machine I am working, so that I load the right modules?

There is 'os.name' and I am sure others which can give you information about what the code is being run on. One can search for the presence of various files or check their contents. I personally add a human readable 'device.txt' file in the root directory which specifies what that particular machine is.

Instead of trying to work out what a machine is and what is present one can simply use try-except until you get an import which works -

Code: Select all

try    : import PySimpleGUI   as sg
except : import PySimpleGUI27 as sg

That will only give the desired results if the 'unwanted' modules are not available on the systems where they are not wanted. It won't deal with the situation where (for example) you may be choosing between modules that are available on some or all of the systems on which you don't want your script to load them. In that scenario, too, if the failure of the 'try' results from a real problem (other than intentional non-availability) with the relevant module, you may very well not want the alternative module to be silently loaded.

[Elmit]

You could look at /sys/firmware/devicetree/base/model to see what you are running on but how you would then dynamically select the include modules I have no idea...

that fails on Ubuntu. No such file!

[hippy]

You could look at /sys/firmware/devicetree/base/model to see what you are running on but how you would then dynamically select the include modules I have no idea...

that fails on Ubuntu. No such file!

Which is therefore a perfect indicator that it's not running on something which does have that file.

There probably won't be a single thing which uniquely identifies every machine you may have. It will be a process of determining what there is and what there isn't - 'twenty questions' if you like - which will hopefully come up with the answer.

[RaTTuS]

look at
/etc/os-release along with
/proc/cpuinfo
/etc/issue
/etc/rpi-issue
and files you put there fir ID purposes