See review D26434 for details, but tl;dr this is a stopgap measure to prevent this port from being removed for being Python 2-only.
(In reply to Charlie Li from comment #0)
Thanks for this!
*** Bug 249588 has been marked as a duplicate of this bug. ***
Created attachment 218388 [details]
Proposed python3 hack
Try this instead? We could continue to pull the daily builds, then run it through 2to3 (ick) there are still a few python files that need special patching.
I don't have an interface to test with. :-(
There are more than a few files that need special attention after running 2to3. Not only does the py3 branch reflect that, but even my attempts to run under Python 3 on the default branch essentially only gets the first screen of the pygobject-based GUI running; dialogs and radio programming do not work at all. Both branches also have pygtk2-isms that need pruning/refactoring because they don't work under pygobject despite the latter's compatibility "layer"; the import and export dialogs are prime examples of not functional. This is what I mean by our (as in what's in phab) patches not going upstream for now, since there is *that* much work and cleanup to do in the default branch.
The wxPython-based GUI is very much still half-baked (and hasn't had much activity since way earlier this year it seems), I would say in an even worse usability state than pygobject. Not to mention that it feels significantly slower.
chirp got removed this morning because we passed the expiration date, would you like to revive it with your python3 fix or should I?