To provide a little bit of hope:

I recently when through updating TwoToneDetect from Python 2.7 to 3.X. I had been putting it off for a long time and was dreading it, but in the end it didn't end up being as bad as I had feared. I used 2to3 as a starting point and that took care of easy stuff like print statements, and then after that just started tackling the error messages one at a time...after a few of those...all of a sudden it worked. What I had anticipated taking weeks ended up only taking a few hours. OP25 is certainly more complex and will likely take more effort, but hopefully it'll be a similar experience.

Andy

On Sat, Feb 15, 2020 at 10:29 PM <op25@zellners.com> wrote:

Quoting Graham Norbury <gnorbury@bondcar.com>:

> I'm traveling at the moment and can't fully respond, but I will say up
> front that op25 is fundamentally not python3 compatible. Lots of rework
> will be required... :(
>

Thats what I figured... and thats why my own Python stuff is not
compatible with 3.x...I'd really like to find these people who feel
the need to change stuff that breaks things and flog them.

I am none to happy with things moving in this direction be GNUR or
just in general.. I'd honestly like to see python3 rm -r *'d from the
planet and just improve 2.x WITHOUT BREAKING THE ABI! Buttttt nooooo!
We can't be that sensible.

Not exactly sure what my plan is on my little programs as they are
mission critical for me/work..Move to some 18.04 VM's/LXC's and
possibly sit tight there.. I am not a fan of change. :) :) ;)

There is a 2to3 script thing I will run that on things to see where it
flags stuff, it might at least be a good reference point to start
from...

I am working on an updated install.sh for 18.10-19.10 where cmake
fubars up things...and it will flag 20.04 as incompatible and stop
till advised. I'll get that to as soon as I work it all out to my
sanctification.