[issue44933] python3.9-intel64 hardened runtime not enabled

Ned Deily added the comment: > the "reliable way to run under rosetta" is using "arch -x86_64 python3". I > don't particularly like having another executable to accomplish the same goal. Unfortunately, using "arch" is *not* a reliable way in general. It works fine for the initial invocation

[issue44933] python3.9-intel64 hardened runtime not enabled

Ronald Oussoren added the comment: @ned: the "reliable way to run under rosetta" is using "arch -x86_64 python3". I don't particularly like having another executable to accomplish the same goal. -- ___ Python tracker

[issue44933] python3.9-intel64 hardened runtime not enabled

tester added the comment: I found the fix for it earlier today and of course the fix is always right in front of you, you just need to look in the right place lol jokes on me. I orginnaly had this and a few other things in my notarization script to get python notarized. codesign --force --op

[issue44933] python3.9-intel64 hardened runtime not enabled

Ned Deily added the comment: The "python3.x-intel64" executable was added for macOS "universal2" builds by Issue44009 in the 3.9.5 and 3.8.10 releases. As described in the issue and the changelog entries, the rationale is: "Provide “python3.x-intel64” executable to allow reliably forcing macO

[issue44933] python3.9-intel64 hardened runtime not enabled

tester added the comment: oh i didn't now that so thank you so much i will look into that maybe thats where my problem is :) -- ___ Python tracker ___ ___

[issue44933] python3.9-intel64 hardened runtime not enabled

Ronald Oussoren added the comment: I don't know what creates "python3.9-intel64", but this is not created by the regular Python build process. It might be created by one of the build scripts you use. -- ___ Python tracker

[issue44933] python3.9-intel64 hardened runtime not enabled

tester added the comment: This part of the script is used to notarize the python framework and it worked with python 3.9.4 and earlier but with 3.9.5 and 3.9.6 it stopped working because of "/python3.9-intel64", "message": "The executable does not have the hardened runtime enabled. #get curr

[issue44933] python3.9-intel64 hardened runtime not enabled

Ronald Oussoren added the comment: I'm not sure what your question is. But to enable the hardened runtime you need to sign the binaries using ``--options runtime`` as one of the options. -- ___ Python tracker _

[issue44933] python3.9-intel64 hardened runtime not enabled

New submission from tester : When trying too build the python framework using the method below and you try to get it notarized you get the following error. "path": "munkitools-5.5.0.4362.pkg/munkitools_python.pkg Contents/Payload/usr/local/munki/Python.framework/Versions/3.9/bin/python3.9-int