On Fri, Feb 8, 2019 at 7:08 PM Dan Smith via chirp_devel <chirp_devel at intrepid.danplanet.com> wrote:
...
If we get to the point of being able to run under py3 as well as py2, then converting to all native PyGObject would be good of course.
...
I was not yet part of the mailing list when the above was posted, but for what it’s worth, I’m not sure supporting both simultaneously will be worth the effort. In my experience, it’s almost always a non-trivial amount of overhead. That may make more sense if Chirp was a library with widespread downstream dependencies. Being an app, it may only make sense if it’s part of the validation strategy (i.e., test compatible long enough to gain confidence in correctness before dropping the requirement that code must run in Python 2).
Just my $1.05.
Zhaofeng Li and Dan, it looks like you’re making excellent progress, and the division oddities are on your radar, but please let me know if there are chunks or subparts where help is needed. Unicode can be a bit tricky sometimes as well.
--Matt