Asking out of curiosity: why did you choose Riverbank’s python binding instead of Qt’s?
Qt for Python is the "offical Qt" binding but it's not as robust or even supported on some platforms like embedded. It's a bit frustrating.
Still, nice work!
Typically I'm developing in Qt/C++ on a host and then using a custom crosstool chain to recompile for the target. The entire cycle isn't that bad, but it's not instantaneous. Using Python has radically sped up some parts of what I'm doing on the target hardware.