Python Installation misses the required "PyObjC" Module

I keep getting this error after updating to 3.4.1.
I tried running “pip3 install pyobjc” but that also does not solve this problem (I had issues with it as well).

I’ve uninstalled Glyphs completely, downloaded it fresh, installed all the modules again, and then the moment I install any plugin from the plugin manager I get this error message.

Can’t quite figure out whats going on:(

I’m also getting multiple Plugin errors (similar to the other forum posting). Sadly mine don’t go away when I click ignore…

I tried installing pyobjc through terminal and get this message (attached).
Really confused. What am I doing wrong?

Running OS 14.5 (23F79)

error pyobjc.txt (62.8 KB)

Your python installation is broken. How did you install it?

And what python is set in Preferences > Addon > Python Version? Is there a “Glyphs Python” in the list? Can you select it and restart Glyphs?

It seems unusual that pip doesn’t use precompiled packages for pyObjC, but tries to compile them on your machine.

When I check on pypi, indeed there are no files for pyObjc-framework-Metal for pyObjc 12 and Python 3.9. Maybe you can upgrade to a newer Python version? Or downgrade pyObjc to 11.1, which still supplied Python 3.9 files.

err..no idea? haha. I originally had just installed from the Modules in Plugin Manager I think.
I deleted that version — using build 3420 now.

Will update.

Yes @GeorgSeifert says I should reinstall Python anyways.

Ran into the same issue. I was on a homebrew Phyton version Python – switching it back to the Glyphs version (inside preferences) solved all issues for me.

1 Like

Same issue here. :sad_but_relieved_face:

I’ve tried to re-install Python in multiple ways but error keeps showing — and therefore scripts and plugins don’t work.

It happens since I updated to 3.4.1 (3436)

This seems to be related to the homebrew python. I fixed it that it would pick it up again. So you need to ether install pyobjc in the homebrew python (and get that up to date when you are at it) or switch to the Glyphs python.

2 Likes

I’ve switched it back to Glyphs version inside preferences and it (seems) to work now.