Anyway, I downloaded the latest source through Mercurial, did a brew install pytgtk and ran ./chirpw… and now the “bug” won’t show up. So I’m wondering if maybe there is a problem with my installed runtime vs. the development libraries?
Entirely possible. The current runtime is built from macports and is getting rather old. There have probably been a lot of fixes (potentially macos specific) since it was built.
When you do that brew build, are you getting quartz-enabled GTK or is it running in X11? The latest (old) runtime is quartz native, which is a significantly better experience for the user, so I'd not want to regress. If your runtime *is* modern, then we should consider doing another revision.
I can’t find any instructions on how to build for OS X. I tried running python setup.py build, but I get this message:
nvahalik:08:51 PM:~/chirp.hg$ python setup.py build running build cp: /opt/local/etc/pango/pangox.aliases: No such file or directory
There is not really anything to build. The runtime is a separate thing. The package installer is created with pkgtool (manually) and it just lays down the runtime tree on their system. From there, the .app is just a shell that gets the latest build tree (the actual python code) copied into it during the automated builds. It's just set up to start the python code with the python binary from the runtime when they click on it.
If you want to work on a new package that lays down a new /opt/kk7ds based on brew with a quartz-enabled GTK, then I'm happy to test it and ultimately promote that as the preferred option if it goes well.
Thanks!
--Dan