-
Notifications
You must be signed in to change notification settings - Fork 686
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
py3 prep #8903
Comments
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
I'm also noting something. Renpy 8 bundles certifi, however this may be an issue for long-term support due to expiry. #8399 makes a move to handle certs, however we should look into updating the internal certifi cert bundle as supplying our own vers of certifi fails to load if it's used by a python-package, which hampers the submod compatibility point. |
more breaking changes
other things:
|
I thought we've decided to do in 2 steps: change the urls, then let update to r8 if the system allows. Has something changed? |
didnt we have to use the installer to update users from r6 to r8? |
I'd prefer to support both the installer and in-game update if possible. Why couldn't we use the updater again, I forgot lol? We should probably write the updating process down. |
the build stuff for r8 is using the market thing instead of Mod, since its a different package or platform or whatever it wont just work from lets say a v11 to a v13. I believe we talked about having the cutover be handled through the installer, then post installer cutover we can use the in-game updater again. ok but also - I was thinking about in-game/installer updating when I wrote that. if someone manually pastes a v13 over a pre-last-v12 build then the older update scripts would be necessary probably. We should test what happens when someone does that. |
Looking through my files because I know I had a solution to Ren'Py's persistent signature system that effectively disables it and returns it to the original system we know from r6/7 |
ok lets make that the last thing in the current pr, seems important enough as its related to saves |
Ah, found it, ironically in some emails as I discussed with another user who had a similar issue: python early:
def verify_data_override(data, signatures, check_verifying=True):
return True
renpy.savetoken.verify_data = verify_data_override Should be the only override needed. This basically cuts out any of the signature verification/checking |
I'm not sure why we used We've switched from the installation into
As far as I know it should still work, we can make an alpha release for us to play around and see how it works. |
Also iirc renpy has done some changes to zsync and updater, we will need to make sure that our updater works for post py3 updates. |
primary checklist for things we can do now to make py3 transition easier
NOTE: any changes we make should be 100% compatible with current submods. This includes renames of anything. If a property is moved/renamed, alias the old one.
map
orfilter
return iterators in Python 3.9+, we should check the places where we use those functions. If it needs alist
instead of iterator, we should convert it explicitly (e.g.list(map(..., ...))
).io
libTweak our custom interpolation formatter to alwaysnot worth the performance impacteval
codecs.decode
to test themviewkeys
->keys
They aren't loaded at all (spj log indicates dict iteration issues (dictionary changed size during iteration
).keys()
calls with a list - bad for efficiency, but should be ok in spritepack load code.When changing backgrounds, we get RunTimeErrors indeco_iter_adv
regarding dict size changes during iteration=======================================
notes for myself:
The text was updated successfully, but these errors were encountered: