...but I thought of doing it that way.
But none of this makes any sense at all.
As I said, they completely redesigned the parameter system....
That's totally OK with me. If this works better for you.
But it makes sense i think. I noticed that is with "positional" the same behavior and code area we had with "extrakw" and "extrapos", so i tested it with the same solution there which works for now without much hassle.
This is how in see it whats going on with all this:
1. Nearly 2 years ago they began to work on this parameter stuff. "extrakw" etc. was either "None" or with a value, but
always there. After the change they are
allowed to be missing, so it banged with the old code. You cannot check for a class-vars state that's not even there sometimes, so we did
write some fixes.
2. Now they did rewrite this part and
the same happened to "positional". If i
rewrite this part now, like you in part did i think, we run perhaps the next months after small new bugs from it.
3. Momentan unrpyc still works becuse the RenPy devs put the old stuff as legacy in the parameter rewrite. When they remove it later we
rewrite this again.
4. The commit to this says it clearly: They are not done with redesigning the AST and ATL stuff. When they do the next part we
rewrite this again... We do not know where this goes in the end.
5. I admit, some of the code in "unrpyc" i do not understand or is
hard to follow where it goes and what it does. I did not write this program, so
another dev's code to understand is horror and its on top of it a "
Decompiler". Not the easiest things out there.
6. The "unrpyc" boss said it self: In unrpyc is a lot of old code for py2 and hacks and stuff for older RenPy compatibility etc. So if he has time again, i expect bigger changes in unrpyc. Then is this code for parameters again
rewritten.
7. In May this year ends RenPys py2 support and they throw this all out. I don't want to know what this means... So, i expect the 7.7x version the last we see from py2. Maybe this means we
rewrite then some stuff... again.
No thanks you, a quick fix does for now IMHO. If not, its not the end of the world. I think unrpyc will anyway need to be in big parts
redone. Half of the code out, some
rewritten, half of the old code will still be good. A new version for py3 only and a old one for legacy RenPy is IMHO better to maintain.
BTW: Good work VepsrP.
Greets
