There is a fix already pulled into the master branch. Just not in an actual release yet. Either download from the master branch, run it in IDLE, or use Linux. All of which should fix the issue.
Yup, looks like it was fixed 13 days ago. I should've done my due diligence. Thank you!
Well I thought I had it fixed, I'm actually the one who sent the pull request. I can look at it in about 30-40 minutes and see what the hell I did wrong. If you run it in IDLE it should work for you in the meantime. Windows' Cmd doesn't do well with obscure UnicodeYup, looks like it was fixed 13 days ago. I should've done my due diligence. Thank you!
EDIT: @dojafoja; It still errors out on me. Did you try also?
@dojafoja
I have a database of Wii U games that you can look up and search http://quantumc.at/gamelist.php but I have discovered it's not working anymore, so I'll fix it soon.
Heh, I like the way you're thinking. I asked the same question (more or less) over here:
Honestly I haven't even really sat down on my pc to look at it. I took on a big job at work and I've just been crazy busy, plus it's tax time and I do all my own book work so I've been busy with that too. It doesn't break in Python 2.7 but apparently still breaks Python 3. I thought I tested on both versions of Python when I submitted my pull request to @cearp github. Then @nexusmtz pointed something out on the github issues page that rather embarrassed me. You see, as many times as I've read the script, I never really noticed or payed ANY attention to the already existing log function. This log function does exactly what I tried doing many times before I resorted to wrapping it with repr(), which obviously is a shitty solution since it still breaks in Python 3. I was just trying to get SOME print output, so I read about replacing the un-printable chars with a '?'. I tried many times but was using it wrong obviously so I assumed I had to resort to what I eventually submitted as my pull request. The better solution is already in the script and most of the print statements should just be ran through the existing log function. I just tested this on both versions of Python and didn't break either one, just prints a '?' where the char is instead of the unicode char string representation like I ended up going with. If I get time I could redirect the print statements and submit a new pull request maybe later today. I feel kind of stupid because I swear I tried doing exactly what this log function does but I just couldn't get it to work proplerly, I realize what I was doing wrong now that I see how it's properly used.
No worries, I'm really busy myself as well. Getting FunKiiU to not break with those unicode chars is really simple now. But then I decided that I could just redirect almost all print statements to the existing log function and actually log some stuff. I created a log buffer that my gui could read from as well to provide info to the user. Everything works flawless on Python 2 but writing from the log buffer to an external log file breaks Python 3 when it has those damn unicode characters. I think I could fix it by making my code uglier than it already is, taking one approach for Python 2 and a different for Python3. I really just need time to finish everything I've been working on. I will get to it "soon", hopefully lol.@dojafoja - sorry i've been afk for a while, you need me to log on to github and accept the pull or is everything ok?let me know
@
Sicklyboy:
@
Sicklyboy:
