4.12 Stable/ 4.11 Beta seem hosed by Python3.11 investigating

[doonze]

I had tested on 3 boxes running 3.7-3.10. I have one box on upstream that I just tried it on, and they won't run at all on 3.11 for WHATEVER reason. Thanks python. Looking into it. The problem is, IDE's say all is well. Code is fine. But 3.11 won't even start to run it.

UPDATE: The issue is fixed with v4.20. I'll do more testing later to see if 3.11 has more surprises for me. But the main path of updating is fixed.

[doonze]

The problem was with the way I was using the @DataClass ConfigObj class in module dbobjects. It was a @DataClass holding other dataclases. Pycharms was happy with it, even on 3.11. But 3.11 itself was NOT. It didn't like me using @DataClass to hold an instance of other @DataClass's on init. I had to move creating them to a function inside the class, it was already there doing almost the same thing as it is now, and wasn't much of a change. But now 3.11 is happy. For now. Sometimes I HATE how Python just goes "You know that thing that's worked for the last 8 years? Well, now it doesn't. Out of the blue. You're welcome"

Took longer than it should have to find, but that was self-inflicted. My Exception was too broad and it was masking the real problem.

Direct fix is easy. Download the 4.20 zip, extract dbobjects from it. Copy into the active db directory of the script. But mine was even more hosed up, as the script failed while cleaning up the directory. Not sure why. It copied some OLD files into the functions folder that also had to be replaced. Normally these are overwritten before the move starts, but the app got the exception before it was supposed to due to the 3.11 error.

Not really sure how it got so messed up. It had moved most of the files, and it shouldn't even have started that until it finished updating. I think the restart of the app happened before the first run was done. Then they both failed.

[doonze]

AHHHH HAAAA! I was running Beta v4.0 on that box. And it had the new unzipper. So my additional problems were that all the files got created in the RIGHT directory. Then v4.12 copied the OLD files with the same names to the functions directory (selfupdate.py, and config.py). I didn't test updates from beta as I'm the only one using them I think. And my primary concern was with Stable upgrades. In stable those files are overwritten before they are moved.

Not going to even waist cycles on this. If someone was using Beta, the fix is to just install 4.20 over the top of it, and call it a day.