Works well with pyqt as well. It's a dream environment writing cross platform apps, and since they're compiled, distribution (especially on win/osx) is really simple. Highly recommended!
I'm glad to see that you use PyQt for the GUI. Have you examined PySide as well? It's mostly drop-in compatible with PyQt and has a much better license in my opinion.
PyObjC, which is what is being used here, is nice, but pretty fragile. It relies pretty much on one guy, Ronald Oussoren, who is also one of the py2app maintainers. It often lags behind the pace of macOS development.
I think PyQt is a more robust solution for GUIs, and it gives you cross-platform compatibility basically for free - although packaging is probably a bit harder.
Will have to dig into this. Seems pretty, would be nice to pick apart the API, looks like Python with PyQt is what most utilities are written in. The crux with not being mac/windows is driver performance. It's a bummer it takes such a massive effort to support hardware.
I've had fantastic luck using pyqt5 in the past, but it kind of bothers me that both pyqt and pyside both exist. They look nearly identical, and I never know if I'm using something which will eventually be dead.
If you don't want to pay for a commercial license, just use PySide. It's LGPL-licensed and has nearly exactly the same API as PyQT. So near that when I switched out PyQT with PySide, all I had to do was change two import statements throughout a ~3000 python gui application.
PyQt and PySide was exactly what I had in mind. It'll leak memory, segfault on load 1% of the time, segfault if you call unrelated methods in the wrong order, you'll randomly get QStrings and QExceptions instead of their Python equivalents, and it'll be impossible to debug.
reply