CHIRP

Some first feedback: Chirp currently depends on Python 2.7 (it uses PyGTK).
We are working on a port, but also on ways to package Python 2.7 inside Chirp for short term.
Thanks for your work!

Jaroslav, I can't apply your patch, which seems to have been auto-translated to py3 syntax. The problem is that the syntax is far from the biggest problem in converting these drivers. Just because they're importable after the conversion, doesn't mean they actually work. In the best case, they crash with byte/string issues, and at worst they work enough to put a radio into program mode and then fail, which might cause the radio to reset its memory or worse. The drivers that are importable now are those that I have hand-converted and tested. The effort to do so is quite non-trivial.

I would appreciate if you not package anything from the py3 branch at this point, just because it's in such a half-working state. The wx UI is what I plan to move to at some point, but it's far from usable by regular people, IMHO. I've been trying to do my new driver development with it and there are a number of issues still, aside from all the missing features. The normal gtk UI in compatibility mode also seems to work, but has been very unstable in my experience and there are plenty of things in it that are also not compatible, causing weird crashes or hangs.

I know it's not a great situation, but the distro's decision to remove python2 on principle has made it what it is. I'm going to close this as invalid for clarity (since it's not just syntax that is the problem) and say it duplicates #495, which is the issue I've been using to track py3 work.