Hello,
I’ve tried all the steps to install Python and start writing in the Macro Panel, but it does not seem to respond when I try to run a print line.
For context, I am running Glyphs 3 on a macOS Monterey 12.0.1. Python 3.11.1 is installed and appears when I check for the version on this Mac.
In Glyphs under Preferences, I do see a Python version 3.9.1 (Glyphs) that is selected and offers no other options.
I did see some advice about installing Homebrew, which I tried before doing the reinstall.
At this point, I’m not sure what I need to do, as I have restarted glyphs and my Mac multiple times to see if anything will work.
Perhaps something went wrong with the installation of Python.
Uninstall Python by going to Window → Plugin Manager → Modules and clicking Remove next to Python.
Verify that Python has been uninstalled completely by choosing Script → Open Scripts Folder and looking into the Repositories folder next to the Scripts folder. These should not be a folder named GlyphsPythonPlugin inside Repositories. If there is, manually delete it.
Go back to the Plugin Manager and install Python again. Wait for the installation to complete, then relaunch Glyphs. In the preferences, make sure the Python version ending in “(Glyphs)” is selected, otherwise select it and relaunch Glyphs again.
Thank you! I’ve followed all steps and this still doesn’t seem to resolve the issue. I have also tried using the ‘Clear’ button. When I click it, the code does not clear. So, something is not allowing it to run or clear. Any other suggestions would be helpful.
Hi there,
So for the last few months, I have been able to use the macro window without any issues. I tried to work through another script today, and nothing appeared in the Macro Window when I tried to run the script. I followed the steps again to reinstall Python as I had done when I first had trouble with installation. I also unchecked the box in Addons as well. This time, no success and I just get a message about how no compatible version of Python is installed. I’m just curious if this is a bug with the latest update, as it was working perfectly before.