Installomator VS python

If you have access to a Mac, Installomator is a good encapsulation of shell scripting.

I used to use something like the above script but switched to using Installomator for all apps we use that it supports. It can do the initial install as a push or from Self Service, and then you can set it up to patch software as well. https://github.com/Installomator/Installomator

If you want to make things easy for your users and yourself, take a look at Installomator. It'll unlock a lot of nice workflows for your users, since you could put a specific title's install action available in Self Service and thats always gonna be easier than trying to track down the vendor's URL and finding the right download. It also means you don't have to repackage anything.

Munki is not an MDM and I recently learned there's this project called Installomator that might help.

Looks like you’re trying to update/work with version 4 but the installomator version is still on version 3. I’d suggest using build a label for musescore4

Installomator https://github.com/Installomator/Installomator

Here it says Foundation is part of pyobjc which may be included in certain versions of python3 such as this https://github.com/macadmins/python - Looking at it now, it seems to set itself apart from the developer tools installation of python3 based on it's installation location. So my guess is that it isn't a module installed with CLT's python3.

Installing python (the MacAdmins Foundation distribution of Python) would be as simple as uploading the installomator script to JSS, adding it as a policy payload with "macadminspython" as a parameter.

Sounds like the scripts you have may be written in Python 2, which as others have stated, was pulled in 12.3. You can try running one with a Python 2 or 3 interpreter to see. You could technically deploy your own Python 2 to people and update the shebangs on the scripts to reflect the updated Python binary location. But Python 2 has been deprecated since January 2020 so it's probably best to just update the scripts. I dealt with this myself and am by no means a programmer. We have a critical script that maps printers for people that I had to update. I used something called '2to3' which is I believe an official Python program that does its best to convert Python 2 code to Python 3 in an automated fashion. It did 99% of the work for me. My script was still failing, but it was just a variable that was being concatenated as a byte instead of a string. Once that was fixed it ran fine. And then we started deploying https://github.com/macadmins/python - as others have mentioned. And then just updated the shebang to point to where that Python gets installed as per their instructions.

Removed. I deployed macadmins Python3 https://github.com/macadmins/python and changed the shebang in scripts we use.

Check out https://github.com/macadmins/python