macOS Framework and/or non-Framework builds?

[brettcannon]

Would we want both or only one of those types?

[cmaloney]

https://stackoverflow.com/questions/1444543/differences-between-framework-and-non-framework-builds-of-python-on-mac-os-x -- has some good context for this

[freakboy3742]

In my opinion - a framework build is definitely necessary; without it, any usage of GUI features will be limited in ways that might be unexpected for most users.

Having that framework build usable as a Framework (or XCframework) so that it can be dropped into in an Xcode project would also be useful - that's the use case that BeeWare has.

I'm not sure I see any particular advantage to providing a non-Framework build as well. The primary benefit that I can see is that the general layout is more like a "normal" Unix install, but I'm not sure that actually makes any functional difference to end users.

[geofft]

This might be a silly question but are macOS builds even in scope for this project at the moment? There are already macOS builds on python.org, no?

(As a data point, those are framework builds, and python-build-standalone does non-framework builds and hasn't yet hit any major problems, though I do vaguely believe that there might be problems at some point.)

[emmatyping]

Brett set the goal to cover all Tier 1 platforms, and the current macOS builds are installers rather than portable builds, so macOS is definitely in scope.