configure.py is not helpful for an individual developer #49
Description
So, I barely understand the various forms of IDs and certificates involved in Apple's macOS code signing system. I really don't understand where "Team ID"s come from.
It looks like configure.py cannot be used to set up "I just want to make it compile on my machine for testing locally and maybe giving it to friends who will tolerate all the extra hoops required to tell Gatekeeper to let it run" -- it always needs a "Team ID". For a personal hobby project, I don't know what "team ID" I would expect to have, since Xcode says "personal team" in the team drop-down? I don't know if that would change when/if my Apple Developer registration actually goes through, but I just paid for that earlier today and apparently that takes up to 48 hours or something.
I would patch configure.py myself to configure Xcode in a useful way if I understood a anything about Xcode signing and Xcode's config file format at all, but I don't and Apple's documentation is not very helpful. Manually, I've just gone to the projects where Xcode gives me compilation errors and reset it to "personal team" and the Apple Development cert (after generating one), and that seems to be working. I have no idea what that looks like inside your Python script. Could you please patch configure.py to support the "I just want to build it to test a bugfix I'm trying to write for you, I barely understand this stuff in the first place" scenario?
I feel like Xcode's forcible integration between .xcodeproj and individual choices of canonical code signing identity were designed without a single millisecond of thought towards OSS...