bpo-41100: Support macOS 11 and Apple Silicon (GH-22855)

[sjmulder]

Backport of commit 4176193 to 3.9:

---

Co-authored-by: Lawrence D’Anna [email protected]

• Add support for macOS 11 and Apple Silicon (aka arm64)

  As a side effect of this work use the system copy of libffi on macOS,
  and remove the vendored copy

• Support building on recent versions of macOS while deploying to older
  versions

  This allows building installers on macOS 11 while still supporting
  macOS 10.9.

https://bugs.python.org/issue41100

[the-knights-who-say-ni]

Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA).

Recognized GitHub username

We couldn't find a bugs.python.org (b.p.o) account corresponding to the following GitHub usernames:

@sjmulder

This might be simply due to a missing "GitHub Name" entry in one's b.p.o account settings. This is necessary for legal reasons before we can look at this contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

You can check yourself to see if the CLA has been received.

Thanks again for the contribution, we look forward to reviewing it!

[sjmulder]

I haven't done anything with the codebase before so please be gentle. In particular, I don't know if this is the right way to do a backport pull request.

[ned-deily]

Thanks for the interest but we will be back porting this and other changes to 3.9 soon.

[sjmulder]

Did I do it wrong then? Why can't one submit a backport?

[ned-deily]

Did I do it wrong then? Why can't one submit a backport?

The core developer(s) handling the original merge to the master branch is normally responsible for deciding what and where to backport and we have automatic tools to help core developers do the work. At first glance, that's what I thought had happened here but, if not, thank you for doing the backport work yourself. Especially with this feature, there are still some pieces to be added so it's best to follow our normal workflow, although it would be interesting to know if you had to manually modify any pieces to backport properly. The process is described in the developers guide, primarily here.

[sjmulder]

Thanks for explaining! I used a regular git cherry pick, there were only a few things to clean up. After that, I had to make two more changes:

• Fix _decimal: sjmulder@d7080b5
• Adding search paths to find libbz2.tbd and libz.tbd: sjmulder@e77f5da

These were the minimal changes necessary to get the package building in pkgsrc; there may be more work to do. I’ll be looking forward to the proper release.