After installing the official python-3.13.16-macos11.pkg, a single codesign --verify --strict --verbose=2 check of the installed Python.framework reported “a sealed resource is missing or invalid” and listed added pip launchers and HTML documentation. The separate interpreter launcher passed strict verification and displayed a Python Software Foundation signing identity.
Our framework check was interrupted at a 65,536-byte output cap, so its enumeration is incomplete and normal final exit status is unknown. We have not retried or changed the installation following that check. Is this specific added-resource discrepancy expected from the vendor installer? What supported procedure establishes the installed framework’s integrity and signing identity while addressing the negative seal diagnostic? We are seeking guidance, not a way to ignore verification failures. _______________________________________________ Pythonmac-SIG mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3//lists/pythonmac-sig.python.org Member address: [email protected]
