>>11061
Yeah, it worked pretty good for me. A little spammy, but fast and easy to use. It mostly:
- Put safety parentheses around all my print statements (even though they all already had them)
- Put a safety list() around every iteration over a dict's keys/values/items call
- Changed up some explicit unicode language to str and cleaned up all the u stuff to just
- Did some really helpful urlparse -> urllib.parse and cStringIO -> io.StringIO stuff
This was all stuff I had feared I would have to do myself, so I was happy it was able to catch it all. The code was valid py3 and did boot. Unfortunately, it couldn't handle the encode/decode calls I had all over the place to handle some str/bytes conversion, so I knuckled down and learned how it works in py3 and rewrote the outstanding shit until it booted right.
I am overall very happy with the unicode changes in py3. They realised what was bad in py2 and fixed it all.
I still have a load of bytes/unicode stuff to clean up and test, stuff like object serialisation and network read/write, but that seems to be mostly it. Once I was booting into something stable, video rendering somehow worked right out of the gate.
I wrestled a bit more with pyinstaller today to get a frozen build going, and it was a pretty huge pain in the balls but I think I've figured something out. There's still a CWD issue stopping it getting too far, but all the dlls are loading and the splash screen comes up.
It may require a clean install, and <Win10 users may need Visual Studio Redistributable 2015. I will do testing with several users before I do the proper release so I know this better.
