Another option would be that the AppleScript checks whether the correct Python is installed (or maybe one of several usable Pythons, for example the official Python 3.x installer or a brew installation) and use that if it is. And if no suitable Python is found it could redirect the user to a web page with instructions on how to install a compatible Python.
That is sort-of what Kevin suggests (Point users to a Python installation), but with a bit of automation added. Jack > On 2 Oct 2021, at 16:22, Kevin Walzer <k...@codebykevin.com> wrote: > > > On 9/28/21 1:12 AM, Vincentius Vincentius wrote: >> >> Can anyone help me with advice on how to create and distribute a Python >> runtime (with my applet) ? >> > Point your users to the installer for the Mac version of Python: > > https://www.python.org/ftp/python/3.9.7/python-3.9.7-macosx10.9.pkg > <https://www.python.org/ftp/python/3.9.7/python-3.9.7-macosx10.9.pkg> > There is no simple way to embed a Python installation within an AppleScript > applet. If you're doing that, you might as well all the way and deploy your > script as a full Mac application with Python libraries bundled using a tool > like py2app. > > --Kevin > > -- > Kevin Walzer > Code by Kevin > http://www.codebykevin.com <http://www.codebykevin.com/> > _______________________________________________ > Pythonmac-SIG maillist - Pythonmac-SIG@python.org > https://mail.python.org/mailman/listinfo/pythonmac-sig > unsubscribe: https://mail.python.org/mailman/options/Pythonmac-SIG
_______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org https://mail.python.org/mailman/listinfo/pythonmac-sig unsubscribe: https://mail.python.org/mailman/options/Pythonmac-SIG
