I'd be fine with one PR.

For context, @jmroot is reporting these issues as a maintainer of the MacPorts project which is well-known for providing best-effort support of (much) older versions of Mac hardware and macOS releases.

Since most of the problematic uses were introduced as part of #114099 "Add support for iOS" feature for the upcoming 3.13 release which is still in its alpha stage, my preference would be to treat those as feature fixes and associate any PRs with that issue rather than creating new issues. But I don't have a strong preference about that nor whether to consolidate PRs.

However, I do have a stronger preference about any fix for the pre-existing problematic use in Objects/mimalloc/prim/unix/prim.c since, I believe, that code was essentially vendored into Python from an existing project and thus should be tracked separately and either checked for an existing upstream fix or reported upstream.

Since most of the problematic uses were introduced as part of #114099 "Add support for iOS" feature for the upcoming 3.13 release which is still in its alpha stage, my preference would be to treat those as feature fixes and associate any PRs with that issue rather than creating new issues. But I don't have a strong preference about that nor whether to consolidate PRs.

I've submitted #118073 as a consolidation of the three non-prim.c changes, tagged against the iOS PR.

However, I do have a stronger preference about any fix for the pre-existing problematic use in Objects/mimalloc/prim/unix/prim.c since, I believe, that code was essentially vendored into Python from an existing project and thus should be tracked separately and either checked for an existing upstream fix or reported upstream.

I've opened #118072 to describe the prim.c problem; I've logged the details of my initial investigation there.

Thanks, @jmroot, for reporting the issue(s) and for providing the initial PRs. And, thanks, @freakboy3742, for the follow-ups. Since #118073 incorporates this change, we can close this PR and its issue.