Python: Python.framework should be ad-hoc codesigned about brew

[SMillerDev]

Moving it since the signing happens in brew, and should probably apply to all or none of the frameworks that you can install with brew.

[MikeMcQuaid]

Will review a PR for this but would like to see more requests for this before maintainers work on it as it seems to be a very niche use-case.

[MikeMcQuaid]

Also changing issue to features as this is not a bug.

[carlocab]

@Bo98 @fxcoudert @woodruffw will know more about whether this is a reasonable thing to do.

[AuroraWright]

(For what it’s worth i’d be fine with opening a PR to add this to the Python formulas currently on brew if no issues are raised here)

[Bo98]

Seems OK, but does it actually need --deep? Binaries inside should already be ad-hoc code signed.

[fxcoudert]

I'm not sure why the framework needs to be code-signed, if the binaries/libraries already are. And if so, why is the Python build process not signing it?

[AuroraWright]

Seems OK, but does it actually need --deep? Binaries inside should already be ad-hoc code signed.

You're right, tested without it and it also worked.

I'm not sure why the framework needs to be code-signed, if the binaries/libraries already are. And if so, why is the Python build process not signing it?

Honestly no idea why macOS enforces it like this, but the official build from python.org is also signed

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[MikeMcQuaid]

Sorry, passing on this for now. Will review/consider a PR, though (but cannot promise it will be merged).