Both builds seem to run without further issues. The build has been tested on a macOS 13.2 machine (MacBook Pro 14" (2021, M1)) and on a macOS 10.13.6 virtual machine. When opened, let it by default and click Next. The ad-hoc signing required for M1 based macOS versions is unaffected by this issue. Open VMware Workstation and click on Create a New Virtual Machine or simply press Ctrl + N to open New Virtual Machine Wizard. Iirc, the PyInstaller documentation mentions some issues regarding code signing for 10.13, but since the builds aren't released on the App Store this seems to be mostly insignificant. I've also bumped the runner to use macos-latest since there don't seem to be any observable issues regarding backwards-compatibility. Here, I've used the conda-incubator/setup-miniconda action as replacement. Neither pygame nor any of the other dependencies caused any kinds of incompatibilities, so installing a Python version built against a lower SDK (10.13, in this case) restores High Sierra compatibility.
Since the setup-python action installs libraries built for an macOS 11 SDK, older macOS versions (down to 10.13) weren't supported anymore. 10.13 Download Increased security 1/3 High Sierra is an update of MacOS which focuses mostly on back-end developments and a higher level of user security.
0 kommentar(er)
