Python 2 vs 3 is weird.
Python 3 broke backwards compatability, so 2 continued on for years after 3 came out while modules were converted. That means there can be modules that work on Python 2.7 but don't work on eg 3.1 but do work on 3.8
It's better to use Python 3 since Python 2 has officially EOLed now.
Yes, I had read somewhere about that Python 2 / 3 issue.
I remember doing a similar thing with one of my programs years ago, where I was still doing updates to a version 4, but was simultaneously working on a revamped and improved version 5. In the end, it did my head in and I scrapped version 5, and continue to this day to put up with the flaws in version 4 (though we are at something like version 7 now, and a different version 5 has come and gone). They weren't terrible after all, just that version 5 was a better way of doing things ... or would have been if I had finished it.
The goal here was just to see if the issue is due to the way Python does Timers and if that's changed.
The normal way of disabling download resume wouldn't help you at all, since it'd just skip trying to resume interrupted files the next time they are downloaded, it wouldn't make any difference to the initial download, it would take a fair chunk of code revision to remove the timers, preallocation and use of provided MD5 chunk data to enable the live resume.
I'm still a bit lost with what you are saying, because I never used a version 2 variant of Python with either version of gogrepo.py. So even if your timers in the forked version are different to those (if any) in the original version of gogrepo.py, I don't see the relevance of using version 2 of Python. Please excuse me for being a bit confused about this.
I guess another way to say that last statement, is that the original version of gogrepo.py is not having a timer issue for me with Python 3.7.0. That's not to say the timer issue isn't at fault, it probably is.
It seems a lot of trouble to me, to do whatever I need to do to install a version 2 variant of Python, for what seems a slim chance without any anecdotal evidence it might improve the supposed timer situation.
And like you said, better off sticking with a version of Python that hasn't reached EOL.
Probably in a few months anyway, I will have been able to redo my work and play environment, and move onto a better PC for my Web usage, and so hopefully solve this download speed issue in doing so. Just a bridge too far right now.