-
Notifications
You must be signed in to change notification settings - Fork 38
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
Support Python 3.9 #196
Comments
I have scanned the Python 3.9-related parts of https://docs.python.org/3.9/whatsnew/changelog.html and couldn't see anything obvious. I paid special attention to the modules that are exposed as "safe", simple types and ast. |
Thank you. We should wait for the final release until we officially declare that we support it. Note to self: Python 3.9b4 was the released version at this time. |
https://www.python.org/dev/peps/pep-0596/ mentions Monday October 5th as 3.9.0 release day |
Reviewed change log up to 3.9.0rc2 which is planned as the last non-final release before 3.9-final. So only reviewing the changes in the final release has to be done. |
Additionally the now operations |
Michael Howitz wrote at 2020-10-5 23:09 -0700:
Additionally the operators `|` and `|=` on dictionaries have to be checked to work along the security restrictions.
"zopefoundation/AccessControl#98"
gives examples that already for Python 3.8 (and before)
some "special methods" could be used indirectly by untrusted code.
|
There is nothing problematic between Python 3.9.0rc2 and 3.9.0 final in the change log. |
Conclusion: The new bit-or operators in Python 3.9 do not require changes in RestrictedPython. |
Look through the change log of Python 3.9 for potential issues which need to be handled by RestrictedPython to prevent access to otherwise forbidden data.
The text was updated successfully, but these errors were encountered: