The root cause has been found, the story is in the ticket (https://trac.macports.org/ticket/71103).
The fact that the PyObjC build doesn’t fail when a PyObjC module fails to build threw me off. Nils. > Op 19 okt 2024, om 01:52 heeft Joshua Root <j...@macports.org> het volgende > geschreven: > > On 19/10/2024 10:26, Nils Breunese wrote: >> Joshua Root <j...@macports.org> wrote: >>> PyObjC consists of a number of python modules. Each has its own directory >>> in site-packages: AVFoundation, AVKit, etc. through to WebKit. >> In >> /opt/local/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages >> I see several directories with names that start with pyobjc_framework_. I >> don't see any such directory with Quartz in its name. Should I? Is there >> such a directory on macOS 14 or older when py312-pyobjc is installed? > > Yes. You can see the files installed on different platforms by clicking the > Files links to the right of the Port Health indicators at > <https://ports.macports.org/port/py312-pyobjc/details/>. > > - Josh
