Apparently this is because of the new Gatekeeper requirements in Catalina, where binaries have to be notarized.
I’m with john daniel on this one: This is unlikely to be related to Gatekeeper or notarisation. Specifically:
Gatekeeper only applies if the program is quarantined, and that’s clearly not the case here (because you’re building it locally).
On older systems Gatekeeper only applied to apps, but on 10.15 we started applying Gatekeeper to all programs, including command-line tools run from Terminal. If this were a Gatekeeper problem, you’d see problems regardless of how you start the app.
My question is: how do I notarize a python module? It's a .so file.
On the Mac an
.so
file is typically a shared library (
MH_DYLIB
) and these can be notarised. However, you only need to worry about notarisation when you get to the point of distributing your product such that users download it and it ends up quarantined.
There are many different reasons why an app might crash when run from Terminal but not when launched from the Finder, or vice versa. I’ve recently been discussing this with another developer on this thread. It’s unlikely that your problem has the same underlying cause, but it should give you some insight into how to approach this.
Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware
let myEmail = "eskimo" + "1" + "@apple.com"